Sub-issue of #2631820: [policy, then infra] Bulk update core issues for relevant minor versions.
There are two bulk updates that need to happen each minor:
- After branching 8.8.x
In advance of Drupal 8.7.0-alpha1 (to be released week of March 11), open issues need to be updated that are now listed for 8.7.x to be under 8.8.x. This should ideally happen on the Thursday or Friday before the alpha release, around March 8. Message:<a href="https://groups.drupal.org/node/534845">Drupal 8.7.0-alpha1</a> will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.6.x, we create a separate bulk update like #2900468: Bulk update 8.3.x Drupal core issues to 8.4.x after 8.3.6 with a different message. Open issues need to be updated that are now listed for 8.6.x to be under 8.7.x:
<a href="/project/drupal/releases/8.6.TODO">Drupal 8.6.TODO</a> was released on TODO and is the final full bugfix release for the Drupal 8.6.x series. Drupal 8.6.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.7.0 on TODO. (<a href="/project/drupal/releases/8.7.0-rc1">Drupal 8.7.0-rc1</a> is available for testing.) Bug reports should be targeted against the 8.7.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.8.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>.
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 #2985640: Bulk update 8.6.x Drupal core issues to 8.7.x in advance of alpha1.
Comments
Comment #2
drummAt least the announcement URL https://groups.drupal.org/node/526844 needs to be updated before sending #1.
Comment #3
drummComment #4
xjmUpdated the first with https://groups.drupal.org/node/534845.
Comment #5
Gábor HojtsyPoint 1 sounds good. 8.8.x is now branched, so that can go!
Comment #6
tacituseu CreditAttribution: tacituseu commentedSomething is wrong with testing configuration for 8.8.x, for some reason it isn't respecting
drupalci.yml
, and as a result e.g. FunctionalJavascript tests run with--concurrency "1"
, which makes the whole testrun almost twice as long.Might want to look at that before updating issues.
Comment #7
Gábor Hojtsy@tacituseu: from @mixologic in chat:
Comment #8
tacituseu CreditAttribution: tacituseu commentedPretty much all of the newly configured 8.8.x-dev branch testing:
https://dispatcher.drupalci.org/job/php-7.2-apache_mysql5.5/3005/
https://dispatcher.drupalci.org/job/php-7.2.x-apache_mysql5.5/2836/
https://dispatcher.drupalci.org/job/php5.6_mysql5.5/5581/
Comment #9
drummtacituseu - See #3038596: Mechanism that adds custom drupalci.yml configurations does not detect configs in new branches. for this issue. It should be solved now, we’re double checking the root cause.
Comment #10
drummUpdate #1 will currently get 7,458 issues, which looks consistent with https://www.drupal.org/project/issues/drupal?text=&status=Open&prioritie...
#2004-23: Finer-grained book controls is the test update for review.
Comment #11
drummGábor mentioned this looked good via Slack, and I double checked the links. Starting the updates.
Comment #12
drummUpdate #1 is done. Resetting the status for #2.
Comment #13
drummI believe we are after the last planned bugfix release of 8.6.x now.
Comment #14
drummUn-assigning myself since the issue comment draft needs non-trivial updates.
Comment #15
xjmWe should be able to simply use the second half of the most recent bulk update:
Comment #16
drummThis will currently affect 6,028 issues, which lines up with https://www.drupal.org/project/issues/drupal?text=&status=Open&prioritie..., the exact discrepancy is due to unpublished issues (spam/etc), which will be updated, and never shown in the issue queue Views.
The sample update for review is #16800-21: User interface usability in Delete Node Form
Comment #17
xjmLooks good!
Comment #18
drummThanks! This is now running.
Comment #19
drummThis completed overnight.