To improve core momentum as we work toward a Drupal 8 beta, we are going to try some added structure in the commit schedule around Drupal 8 alpha releases:
-
For several days before each alpha release, we will commit only critical and major patches, to encourage focus on these important issues in preparation for each alpha release. (See the documentation on core issue priorities for more information.)
-
Immediately following the alpha release, there will be "disruption days". Core maintainers will work with patch authors to schedule commits for patches that are difficult to reroll or are likely to break many other patches (for example, patches that touch dozens of files, or make significant changes to key APIs). The goal here is to help contributors know when to reroll these patches for the best chance of a timely commit, and to manage conflicts with critical, major, and beta-blocking issues. Patches that should be scheduled are identified at the core maintainers' discretion. See the Avoid commit conflicts and Will cause commit conflicts issue tags.
After we've tried this schedule for a couple months, we will re-evaluate it to make sure it is having the intended effect.
The release of the next alpha, drupal 8.0-alpha8, will be January 22, 2014. With that in mind, here is the commit schedule for the rest of this month.
|
Wed. Jan. 15 - Tues. Jan 21 |
Only critical and major patches committed. |
|---|---|
|
Wed. Jan 22 |
Drupal 8.0-alpha 8 released. |
|
Thurs. Jan. 23 - Tues. Jan 28 |
Disruptive patches committed at core maintainers' discretion. (Schedule in advance with a core maintainer.) Note that January 25 - 27 will be blocked off from scheduled changes, due to the Global Sprint Weekend. |