Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The big one! Hopefully much shorter than #2485119: [meta] The Drupal 8.0.0-rc1 Release Checklist. :P
Remaining tasks
Core
- #2455081: [policy, no patch] 8.1.x release schedule
- #2550249: [meta] Document @internal APIs both explicitly in phpdoc and implicitly in d.o documentation
- Ensure there are no "critical" or "highly critical" private security issues against D6/D7 core. (link requires security team access)
- Perform final profiling of key scenarios (#2497185: [no patch] Create standardized core profiling scenarios and start tracking metrics for them) to ensure they have not regressed from the targets specified in that issue.
- Test in all supported browsers (including mobile) #2152519: [meta] Make sure Drupal 8 looks good and works right on browsers (both mobile+desktop)
- Ensure no more Drupal.org blockers exist: #2559711: [meta] Drupal.org (websites/infra) blockers to Drupal 8.0.0, 8.1.0, etc. (especially translations and testing for contrib modules)
- Run automated tests against all supported PHP/database versions - especially PHP7, and reconsider #2454439: [META] Support PHP 7, specifically whether we can revert the two workaround commits added in that issue
- #2606334: Update CHANGELOG.txt for the release (compile list of high level changes)
Not Core
- Get a release announcement together
- Make a pretty landing page ala https://www.drupal.org/drupal-7.0
- Translate it into 5000 languages
- Other
Comments
Comment #2
plach5. Party until you no longer remember your name, or the 9.0.x branch is opened, or both?
Comment #3
catchComment #4
RainbowArrayWe should remove core item 2: #2343351: Make picture polyfill optional from this list. We definitely still need to include Picturefill for responsive images. Browser support continues to grow, but it isn't ubiquitous enough to warrant removing the polyfill.
Comment #5
webchickRock.
Comment #6
webchickAdding #2455081: [policy, no patch] 8.1.x release schedule as an explicit checklist item. We should be able to make good progress on this at Barcelona.
Comment #7
webchickMoving #2550249: [meta] Document @internal APIs both explicitly in phpdoc and implicitly in d.o documentation from the RC checklist over to here, per @catch.
Comment #8
xjmShould we add checking CHANGELOG.txt to this as well? The most recent things it mentions are adding Tour and Twig.
Comment #9
catchComment #10
xjmComment #11
cosmicdreams CreditAttribution: cosmicdreams as a volunteer commentedAre we planning on breaking out the completed tasks in this list once they're done. At first glance, it looks like some of these tasks are completed.
Comment #12
xjmNope, those are prior related issues. All the steps are things that we need to do (again, in some cases) as part of preparing for the release. And starting on it is postponed until after RC1, at least, and probably until around when we make a decision about the release date.
I don't know why #2212151: Document/test updating active configuration based on API changes (i.e. plugins) was on there though. Removing that.
Comment #13
webchickWrong d.o blocker issue.
Also removing the Version constant from the checklist; that's in the docs already at https://www.drupal.org/node/721106.
Comment #14
catchComment #15
xjmIt's time.
Comment #16
xjmComment #17
dawehnerComment #24
xjmlol. I forgot that this was still open.
We have followups for 8.0.1+ and 9.0.0, so we don't need this tracking issue. Marking fixed and setting it back to 8.0.x. :)