Skip directly to content

When it's ready™

on Tue Oct 8, 2013

This is the third in a series of posts on Drupal 8's progress toward release.

During Drupal 8's clean-up phase, the critical technical debt in Drupal 8 rose significantly. In the three months since the end of the clean-up phase and the start of the API completion phase, we've started to catch up, fixing nearly as many critical issues as we've filed. We're about to turn a corner in Drupal 8's progress toward release, but now we need to start fixing more issues than we find. Details follow.

Debugging, OCTO style: Where every field has a name

on Tue Sep 3, 2013

Uncaught PHP Exception Drupal\field\FieldException: "Attempt to create an unnamed field." at /Users/jbeach/code/drupal/core/d8/core/modules/field/lib/Drupal/field/Entity/Field.php line 225

effulgentsia is on the case:

Making your way with Drupal today takes everything you've got
Taking a break from all your worries, sure would help a lot
Wouldn't you like to get away?
Sometimes you want to go where every field has a name

Triaging Drupal 8

on Thu Aug 8, 2013

This is the second in a series of posts on Drupal 8's progress toward release. Read on for how you can help.

A month ago, I wrote about the growing technical debt in Drupal 8 core, and the impact this would have on Drupal 8's release date. Since that post, 88 of Drupal 8's major and critical issues have been fixed. The week of API freeze, we reached an all-time record of 35 of these top-priority issues fixed in a single week, among 84 total core commits that week.

Wanted: Core taxonomy co-maintainer

on Wed Jul 24, 2013

I'm looking for someone to help me manage core taxonomy issues and to join MAINTAINERS.txt. You don't have to be an expert, just show up. :) See below for details.

Technical debt in Drupal 8 (or, when will it be ready?)

on Fri Jun 28, 2013

This is the first in a series of posts on Drupal 8's progress toward release.

We're coming up fast on Drupal 8's API freeze deadline of July 1, when the Drupal community will stop changing Drupal 8 APIs, start porting contributed modules, and focus on polishing Drupal 8 (or, in other words, making it releasable). But what does that mean, exactly?

We'll create our first release candidate for Drupal 8 when there are no known critical issues remaining. Based on that information, and on the rate at which we've been fixing criticals, estimates that the release date for Drupal 8 will be... ready for it?...


Did I scare you yet?

Well, okay. Before you fire all your developers and migrate your sites to Joomla, let's take a closer look. Since the Drupal 8 API isn't stable yet, many developers are still -- for four more days -- focusing on making API changes. Typically, some of these changes will accidentally introduce bugs that we don't discover until later. After July 1, everyone's focus should shift to fixing our outstanding bugs and release blockers.

Still, the number of critical issues has been steadily increasing over the past six months. This wasn't the case earlier in the release cycle, and without lots of work, it's going to affect how soon (or not) Drupal 8's myriad improvements are available to the world.