The goal of this issue is to discuss how and when we branch and release 8.1.x.
Proposed schedule
| November 19, 2015 | 8.0.0 released |
|---|---|
| January 6, 2016 | 8.1.x may open to new feature development, at committer discretion, based on pending prioritized features and critical and major technical debt. Note: some minor-version-only bug fixes and prioritized features may be committed to 8.1.x before this date. |
| February 24, 2016 | 8.1.0-beta1 released. 8.2.x may open to new feature development, at committer discretion, based on pending prioritized features and critical and major technical debt |
| March 16, 2016 | 8.1.0-rc1 released. Similar requirements to 8.0.0-rc phase for patches to go into 8.1.x after this point. |
| April 20, 2016 | 8.1.0 released |
| August 17, 2016 | 8.2.0-beta1 released. 8.3.x may open to new feature development, at committer discretion, based on pending prioritized features and critical and major technical debt |
| September 21, 2016 | 8.2.0-rc1 released. RC rules apply. |
| October 12, 2016 | 8.2.0 released. |
See also
- Drupal 8 is currently in beta: #2350615: [policy, no patch] What changes can be accepted during the Drupal 8 beta phase?
- The next possible milestone is supporting a beta to beta upgrade path: #2341575: [meta] Provide a beta to beta/rc upgrade path
- The plan for the release candidate phase and the release of 8.0.0 is outlined in: #2362647: [policy, no patch] 8.0.0 release candidates, release, patch versions
- A plan to support semantic versioning with six-month minor releases of 8.x.x is documented in: #2135189: Proposal to manage the Drupal core release cycle