From ff721450db40098d20346642ef67ff0e22ad54da Mon Sep 17 00:00:00 2001 From: Jesse Luehrs Date: Wed, 20 Jun 2012 13:18:14 -0500 Subject: [PATCH] add release branch steps to rmg --- Porting/release_managers_guide.pod | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index d442f84..8ab01d6 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -457,6 +457,16 @@ L<"Building a release - advance actions"> to ensure they are all done and up-to-date. +=head3 create a release branch + +For BLEAD-POINT releases, making a release from a release branch avoids the +need to freeze blead during the release. This is less important for +BLEAD-FINAL, MAINT, and RC releases, since blead will already be frozen in +those cases. Create the branch by running + + git checkout -b release-5.xx.yy + + =head3 bump version number For a BLEAD-POINT release, if you did not bump the perl version number as @@ -977,6 +987,18 @@ Use the template at Porting/release_announcement_template.txt Send a carbon copy to C +=head3 merge release branch back to blead + +If you made a release branch for this release, merge it back into master now, +and delete it. + + git checkout blead + git pull + git merge release-5.xx.yy + git push + git push origin :release-5.xx.yy + git branch -d release-5.xx.yy + =head3 update epigraphs.pod Add your quote to F and commit it. -- 1.8.3.1