The State of Drupal 8: July 2014

drupal 8 logo

It’s been 8 months since our last overview of Drupal 8.

A good number of OSTraining members went to DrupalCon Austin or to DrupalCamps this summer and came back with questions about Drupal 8.

So, here’s an update on Drupal 8 and when you can plan on using it.

Where is Drupal 8 currently?

The current version of Drupal 8 is Alpha 13. Alpha versions are officially described this way:

“These are the first to come out, and are therefore the least stable. Most reported errors are resolved but there are most likely still outstanding known issues, which might include security issues.”

In short, you can’t use alpha versions for real sites. They may have serious unpatched flaws and there’s no upgrade path from one release to the next.

There have been 13 alpha releases, but that phase is nearly at an end. After alpha releases, there are 3 more steps:

  1. Beta versions
  2. Release Candidates
  3. A Stable release

Step #1. Beta versions

There are now 7 issues that are serious enough to block a Beta release. There were more than twice as many at Drupal Con Austin last month. So, there’s a very good chance that we’ll see a release of the first Drupal 8 beta in late July or in August.

What is a beta version? It means that APIs are meant to be stable and so module developers can safely start to update their modules.

It also means that there should be an upgrade path from each beta version to the next so you continuously develop a site.

Step #2. Release Candidates

Once there are no critical bugs in the beta releases, the next step is a release candidate.

At the moment there are around 90 critical bugs. shows critical bugs in red. It’s fair to say, at the current rate of progress, that a release candidate is unlikely in 2014.


Step #3. A stable release

We’re going to get a beta version very soon, but enough critical bugs remain that we’ll likely see a long release candidate phase.

At DrupalCon Austin, Dries predicted a stable release “early to the middle of next year”.

Time to get it done

Drupal 8 was designed to be the most ambitious and best Drupal release ever. It still will be, but there’s been a noticeable shift in attitude lately. The most recent official Drupal core update said this:

“It’s time to get Drupal 8 done. We need to stop making large, non-essential changes, because every time we make more work for ourselves, we delay the release of 8.0.0 for hundreds of thousands of people. When we have a choice between doing something quickly and imperfectly, or slowly and perfectly, it’s time to pick the quick, imperfect fix.”

Dries said something similar in his Austin keynote:

“We need to be smarter about what we see as critical bugs. Is this really critical or can it be fixed in 8.1?”

Drupal 8.1?

Yes, the Drupal release cycle is changing with Drupal 8. This blog post has a full explanation of the new cycle.

One of the most important changes is that Drupal 8 will have several releases with new features. New Drupal 8 releases will come out every 6 months and will be called 8.1, 8.2, 8.3 etc.

This means that some key Drupal 8 features can be put on hold for 6 months to enable a quicker release of Drupal 8.0. Ideally, that should help speed up the final release.

So when can I start using Drupal 8?

  • Testing = Now: You can download and test Drupal 8. allows you to test Drupal 8 online. You can also download the files from
  • Development = From August: Theoretically, there should be stable APIs and an upgrade path between each beta release so you can start developing more seriously.
  • Real sites = Summer 2015: You have a good chance of seeing a stable Drupal 8 and using it for live sites.

Drupal Explained is the best-selling Drupal book and we’re not plannng to start updating it for Drupal 8 until the spring of 2015. I suspect that when most business will start to take a serious look at using Drupal 8.


  • Steve Burge

    Steve is the founder of OSTraining. Originally from the UK, he now lives in Sarasota in the USA. Steve's work straddles the line between teaching and web development.

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
9 years ago

‘It’s time to pick the quick, imperfect fix’!!
Why not, you know, just use a stable framework like Django or Rails instead of putting yourself through all this pain..

9 years ago
Reply to  anon

Hi Anon,
Even with frameworks, those types of choices have to be made. There’s a balance between perfection and good.
By the way, Drupal 8 is being built using the Symphony PHP framework.

Brian Osborne
Brian Osborne
9 years ago
Reply to  anon

Drupal is not comparable to MVC frameworks like Django and Rails. Drupal comes with many “out of the box” content management features that those frameworks don’t. While it’s quite possible to create a CMS using them, it takes a lot more manual work to get it to that point. Likewise, Rails and Django are much better in their own regard for certain applications.

9 years ago
Reply to  Brian Osborne

Yep, Drupal is not MVC. It is PAC and that should mean Better maintainability.

9 years ago

We are using Drupal 6.31, as we await Drupal 8. We have been awaiting to redesign. Should we upgrade to Drupal 7 ??? We had planned to skip 7.

9 years ago
Reply to  Tom

Hi Tom
It does depend on your time scale of course. If you want to launch in the next year, you’ll need to go with 7.
It’s worth noting this: [url=]…[/url] Your Drupal 6 site will probably be get security updated until next fall.

Would love your thoughts, please comment.x