>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3524366. --> Reported by: [jonathan1055](https://www.drupal.org/user/92645) Related to !360 !359 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Core 11.2.x branch has been created so should we update the value of <code>CORE_NEXT_MINOR</code> from 11.1.x-dev to 11.2.x-dev?<br> <a href="https://www.drupal.org/project/drupal/releases">https://www.drupal.org/project/drupal/releases</a></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>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</li> <li>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</li> </ul> <p>See <a href="https://www.drupal.org/project/gitlab_templates/issues/3524366#comment-16115203">comment #13</a> for a full example with real versions and release dates.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3>