@@ -83,7 +83,11 @@ Micro versions should instead read::
8383Check all active milestones for consistency. Older milestones should also backport
8484to higher meso versions (e.g. ``v3.6.3 `` and ``v3.6-doc `` should backport to both
8585``v3.6.x `` and ``v3.7.x `` once the ``v3.7.x `` branch exists and while PR backports are
86- still targeting ``v3.6.x ``)
86+ still targeting ``v3.6.x ``).
87+ 88+ Close milestones for versions that are unlikely to be released, e.g. micro versions of
89+ older meso releases. Remilestone issues/PRs that are now untagged to the appropriate
90+ future release milestone.
8791
8892Create the milestone for the next-next meso release (i.e. ``v3.9.0 ``, as ``v3.8.0 ``
8993should already exist). While most active items should go in the next meso release,
@@ -294,9 +298,15 @@ it is important to move all branches away from the commit with the tag [#]_::
294298
295299 git commit --allow-empty
296300
301+ Push the branch to GitHub. This is done prior to pushing the tag as a last step in ensuring
302+ that the branch was fully up to date. If it fails, re-fetch and recreate commits and
303+ tag over an up to date branch::
304+ 305+ git push DANGER v3.7.x
306+ 297307Finally, push the tag to GitHub::
298308
299- git push DANGER v3.7.x v3.7. 0
309+ git push DANGER v3.7.0
300310
301311Congratulations, the scariest part is done!
302312This assumes the release branch has already been made.
0 commit comments