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.We are slowly picking up a list of tasks that need to be done prior to release, but should not really count towards issue count thresholds because there's nothing much can be done about them until we're closer to an 8.0 release, or alternatively they rely on things like Drupal.org infrastructure changes rather than core.
All those issues are at:
How to help
Since we are closing down on the list of beta blockers, it's the right time to triage the issues 'revisit before beta'
We tried to do this in D7, but I don't think all the tagged issues actually got revisited prior to release, so to make sure that happens this time, let's have one critical task to keep an eye on that tag.
Do not tag this issue with "revisit before release" or demote it to normal, or I will hunt you down.
Probably what we could do is bump the actual core items like jQuery minification to critical once we hit beta or something like that.
Comments
Comment #1
plachNice! Marking postponed
(just joking :)
Comment #1.0
plachUpdated issue summary.
Comment #2
xjmWe should also be sure to check closed issues; e.g. #1463564: Drupal 8 does not work with PHP 5.3.2 (the version shipped with Ubuntu 10.04 LTS).
Comment #3
catchThere's 52 of these at the moment. Some of the issues haven't been updated for over 18 months so if anyone fancies some queue triage, getting that list down to the ones that really do need to be revisited would be very helpful.
http://drupal.org/project/issues/search/drupal?status%5B%5D=Open&issue_t...
Comment #4
catchIf we're actually going to revisit anything, it needs to happen before beta so there's time to make changes before RC.
Comment #4.0
catchUpdated issue summary.
Comment #5
ianthomas_ukSome of these will need to be postponed until after beta, and some are reminders to do some manual testing (e.g. #2152519: [meta] Make sure Drupal 8 looks good and works right on browsers (both mobile+desktop)).
Can I suggest we split this into 3 tags:
- revisit before beta (renamed from the current tag)
- revisit before rc
- revisit before 8.0 (deliberately not the same as the current tag, so people will realise it has changed)
Comment #6
catchThat works for me. If we're re-tagging stuff, that's by definition revisiting it anyway ;)
Comment #7
catchComment #8
ianthomas_ukIs there a way to rename the current "revisit before release" tag to be "revisit before beta", or should I go through the tagged issues and change them?
Comment #9
catchDone.
Comment #10
catchComment #11
catchOK tag is reviewed ;)
I did one of the following for each issue:
-> won't fix
-> beta target (i.e. this is an active issue it'd be nice to get in before/around the first beta)
-> critical
-> duplicate
-> just untagging because I couldn't see why we'd explicitly need to sort that issue out before beta
-> needs more info / grumpy 'why is this not critical then?' comment.
-> revisit before release candidate
We'll likely need to go through the beta targets before a beta, but that list is much more up to date than this, so moving this to cover issues that need looking over prior to RC.
Comment #12
David_Rothstein CreditAttribution: David_Rothstein commentedYou missed a bunch:
https://drupal.org/project/issues/search?projects=Drupal+core&issue_tags...
I'm guessing you only looked at open issues, but closed issues - or at least "closed (fixed)" issues - are some of the most important ones where this tag was added (i.e., issue was fixed, but with the idea of revisiting the fix later).
I helped out by removing it from a few now where it looked obviously obsolete:
#1463564: Drupal 8 does not work with PHP 5.3.2 (the version shipped with Ubuntu 10.04 LTS)
#1751100: Bump minimum version of php required to 5.3.5
#2004836: Disable overlay in standard profile
But otherwise there's still a lot of them to look at.
Comment #13
drifter CreditAttribution: drifter commentedUpdated summary with the correct tags (previous link was broken).
Comment #14
catchTagging novice - it should be possible to triage this without massive amounts of 8.x experience.
Comment #15
catchComment #16
catchComment #17
catchComment #18
catchComment #19
catchComment #20
xjmComment #21
xjmComment #22
xjmComment #23
catchNIce one clearing the last couple of issues out. Untagging beta blocker - we'll need to do this again before RC.
Comment #24
xjmHm we added the "revisit before release candidate" tag but there are still/again these:
https://www.drupal.org/project/issues/search/drupal?project_issue_follow...
I forgot and tagged a couple issues with it this morning.
Comment #25
ianthomas_ukI've had a look through that list and there's nothing that I'd say needs to be addressed before beta. There are several that are documentation issues that are waiting for a bit more API/UI stability.
Comment #26
catchComment #27
catchComment #28
catchComment #29
catchComment #30
xjmComment #31
dawehnerI count 12 not postponed issues.
Comment #32
xjmClosing as a duplicate of our new RC checklist #2485119: [meta] The Drupal 8.0.0-rc1 Release Checklist per discussion with @webchick, @alexpott, @effulgentsia, and @catch.
Comment #33
xjm