Bulk updates for this minor:

  1. 8.8.x → 8.9.x done!

    After branching 8.9.x:

    In advance of Drupal 8.8.0-alpha1 (to be released the week of October 14th), open issues need to be updated that are now listed for 8.8.x to be under 8.9.x. All the issues listed for 9.x should be bulk updated for 9.0.x when the branch is opened. This should ideally happen on the Thursday or Friday before the alpha release, around October 10th. Message:

    <a href="https://groups.drupal.org/node/535412">Drupal 8.8.0-alpha1</a> will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9's release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the <a href="/core/release-cycle-overview#minor">Drupal 8 and 9 minor version schedule</a> and the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a>.

  2. 9.x → 9.0.x all issues, including closed ones

    Shortly after 8.9.x is branched, 9.0.x will be as well. Once 9.0.x is available, all issues currently filed against 9.x should be moved to 9.0.x. Message:

    The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a> and the <a href="/node/3007300">Drupal 9.0.0 release plan</a>.

  3. 8.7.x → 8.8.x around November 4th 2019

    Separately, after the last planned bugfix release of 8.7.x around November 4th 2019, we perform a separate bulk update for patch-eligible issues. Open issues that are now listed for 8.7.x need to be moved to 8.8.x:

    <a href="/project/drupal/releases/8.7.9">Drupal 8.7.9</a> was released on November 6 and is the final full bugfix release for the Drupal 8.7.x series. Drupal 8.7.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.8.0 on December 4, 2019. (<a href="/project/drupal/releases/8.8.0-alpha1">Drupal 8.8.0-alpha1</a> is available for testing.)
    
    Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the <a href="/core/release-cycle-overview#minor">Drupal 8 and 9 minor version schedule</a> and the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a>.

A script used to do this is available in #2631820-25: [policy, then infra] Bulk update core issues for relevant minor versions.

Comments

xjm created an issue. See original summary.

xjm’s picture

Issue summary: View changes
xjm’s picture

Issue summary: View changes

svettes could also be granted issue credit for this issue.

drumm credited svettes.

drumm’s picture

Assigned: Unassigned » drumm
drumm’s picture

Issue summary: View changes
Status: Active » Needs review

Test for 1. 8.8.x → 8.9.x, needs confirmation to proceed.

This will currently get 8,468 issues, which is consistent with https://www.drupal.org/project/issues/drupal?text=&status=Open&prioritie...

The test issue update is #2004-24: Finer-grained book controls

drumm’s picture

Issue summary: View changes

Test for 2. 9.x → 9.0.x, needs confirmation to proceed.

This will currently get 113 issues, which is consistent with https://www.drupal.org/project/issues/drupal?text=&status=Open&prioritie...

The test issue update is #1380720-207: Rename entity "bundle" to "subtype" in the UI text and help

xjm’s picture

The 8.9.x bulk update looks good. There's a couple typos in my brand-new text for 9.0.x; I'll update the IS.

xjm’s picture

Issue summary: View changes

Updated the 9.0.x text to:

The 9.0.x branch is open for development, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the <a href="/core/release-cycle-overview#minor">Drupal 8 and 9 minor version schedule</a>, the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a>, and the <a href="/node/3007300">Drupal 9.0.0 release plan</a>.

xjm’s picture

Issue summary: View changes

Actually 9.0.x isn't actually open for development yet since we can't run tests for it yet. So changing it to:

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the <a href="/core/release-cycle-overview#minor">Drupal 8 and 9 minor version schedule</a>, the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a>, and the <a href="/node/3007300">Drupal 9.0.0 release plan</a>.

xjm’s picture

Issue summary: View changes

...Meh, the minor version schedule part isn't really relevant for 9.0.x, so updating that...

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a> and the <a href="/node/3007300">Drupal 9.0.0 release plan</a>.

drumm’s picture

Issue summary: View changes

New test for 9.x → 9.0.x needs review: #1591634-6: don't say "content" when we mean "contents"

drumm’s picture

Issue summary: View changes

1. 8.8.x → 8.9.x is now running

xjm’s picture

OK, the 9.0.x update comment looks good now too.

drumm’s picture

Issue summary: View changes

1. 8.8.x → 8.9.x finished overnight.

I’m starting 2. 9.x → 9.0.x now.

drumm’s picture

Issue summary: View changes
Status: Needs review » Postponed

2. 9.x → 9.0.x is done

Postponing this issue until the 3rd update is ready.

drumm’s picture

Issue summary: View changes

9.x → 9.0.x, closed issues are now migrated, too.

xjm’s picture

Issue summary: View changes
Status: Postponed » Active

https://www.drupal.org/project/drupal/releases/8.7.9 is in packaging, so the final bulk update can happen shortly.

drumm’s picture

Status: Active » Needs review

Test for 3. 8.7.x → 8.8.x, needs confirmation to proceed.

This will currently get 420 issues, which is consistent with https://www.drupal.org/project/issues/drupal?text=&status=Open&prioritie...

The test issue update is #47709-24: private://logo.png gets a 403 for custom logos

xjm’s picture

We now have the beta available so we should link that instead I think. Updated text:

<a href="/project/drupal/releases/8.7.9">Drupal 8.7.9</a> was released on November 6 and is the final full bugfix release for the Drupal 8.7.x series. Drupal 8.7.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.8.0 on December 4, 2019. (<a href="/project/drupal/releases/8.8.0-beta1">Drupal 8.8.0-beta1</a> is available for testing.)

Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the <a href="/core/release-cycle-overview#minor">Drupal 8 and 9 minor version schedule</a> and the <a href="/core/d8-allowed-changes">Allowed changes during the Drupal 8 and 9 release cycles</a>.
drumm’s picture

drumm’s picture

Status: Needs review » Reviewed & tested by the community

Looks like this is okay, I’ll go ahead and run this.

drumm’s picture

Status: Reviewed & tested by the community » Fixed

Done!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.