11.2.x is released - update CORE_NEXT_MINOR

Migrated issue

Reported by: jonathan1055

Related to !360 (merged) !359 (merged)

Problem/Motivation

Core 11.2.x branch has been created so should we update the value of CORE_NEXT_MINOR from 11.1.x-dev to 11.2.x-dev?
https://www.drupal.org/project/drupal/releases

Proposed resolution

  • As soon as a development branch for the next minor is created, switch to using that branch for the 'Next Minor' variant. For example 11.2.x-dev should now be used, not wait for 11.2.0-beta
  • When there is no such branch, for example when the minor release has just moved forward, say from 11.m.n to 11.(m+1).0 and there is no 11.(m+2).x-dev branch, then revert back to using 11.x-dev

See comment #13 for a full example with real versions and release dates.

Remaining tasks

Assignee Loading
Time tracking Loading