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.Sub-issue of #2631820: [policy, then infra] Bulk update core issues for relevant minor versions.
There are two bulk updates that need to happened each minor:
-
In advance of Drupal 8.4.0-alpha1 (to be released week of July 31), open issues need to be updated that are now listed for 8.4.x to be under 8.5.x. This should ideally happen on the Thursday or Friday before the alpha release, around July 28. An adapted message from #2631820-30: [policy, then infra] Bulk update core issues for relevant minor versions for that would be:
<a href="https://groups.drupal.org/node/517148">Drupal 8.4.0-alpha1</a> will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the <a href="/core/release-cycle-overview#minor">Drupal 8 minor version schedule</a> and the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 release cycle</a>. - Separately, after the last planned bugfix release of 8.3.x, we create a separate bulk update like #2846813: Bulk update 8.2.x Drupal core issues to 8.3.x after 8.2.6 with a different message.
A script used to do this is available in #2631820-25: [policy, then infra] Bulk update core issues for relevant minor versions.
This is a successor issue to #2846809: Bulk update 8.3.x Drupal core issues to 8.4.x in advance of 8.3.0-alpha1 (Jan. 31 or before).
Comments
Comment #2
xjm@catch and I agreed that we'll make the 8.5.x branch shortly before this happens, to minimize the time we cherry-pick things across three branches. I have making a new core branch automated now, so it should not take long. We'll branch in advance of whenever infra will have time to kick off the bulk update; just let us know.
Comment #3
xjmComment #4
drummWill do, please un-postpone when 8.5.x is branched.
Comment #5
xjm8.5.x is in packaging now: https://www.drupal.org/project/drupal/releases/8.5.x-dev Unpostponing!
Comment #6
xjmThis was supposed to happen at the end of last week; any update?
Comment #7
drummSorry, I managed to forget about this. Updating a test issue in the next few minutes.
Comment #8
drummThis will currently affect 5,081 issues, which looks consistent with https://www.drupal.org/project/issues/drupal?text=&status=Open&prioritie...
Comment #9
drummTaking the liberty of replacing “was released the week of July 31, 2017” with the specific date, see issue summary.
Comment #10
drumm#2780: How About a Book Javascript TOC Tree is the updated test issue. Confirmed all the links go to places and I don’t see any copyediting problems.
Comment #11
prestonso CreditAttribution: prestonso commentedSince we haven't technically released the alpha due to CI issues, can we change
was released July 28, 2017towill be released the week of July 31, 2017to reflect that the release hasn't occurred?Comment #12
prestonso CreditAttribution: prestonso commentedUpdating IS to reflect #11.
Comment #13
drumm#2946: Login fails and no warning is issued if cookies are not enabled is the next test issue for review.
Looks like I managed to read over the specific release the date referred to.
Comment #14
prestonso CreditAttribution: prestonso commentedLooks awesome! Thanks @drumm. RTBC.
Comment #15
drummThe script is now running, and will take a couple hours. (It is rate limited to keep caches as happy as caches are capable of being.)
Comment #16
xjmThe comment on #2946: Login fails and no warning is issued if cookies are not enabled looks correct, thanks!
I'm going to add some clarifications to the summary that this first migration happens in advance of the release, since the summary is not quite right and people seem to get confused about it a good bit. This bulk update was supposed to be done at the end of last week. If 8.5.x needed to be achieved earlier in order for the bulk update to to happen on July 28, then we would have needed to know that in response to #2.
There's a separate update that happens after the release, for the bugfixes, similar to #2846813: Bulk update 8.2.x Drupal core issues to 8.3.x after 8.2.6.
Comment #17
xjmOr, as a timeline:
Comment #18
drummIssue updates have completed.
Comment #19
xjmThanks @drumm!
We'll file a followup for the next bulk update similar to #2846813: Bulk update 8.2.x Drupal core issues to 8.3.x after 8.2.6, which should happen later this week once the patch release ships.