postgres.git / summary / log / commit / refs

commit    f32609db72f07d6477a4c7de2565cb244f2af969
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Thu Jun 14 02:11:06 2012 +0000
First released in: 9.3.0

    Flesh out RELEASE_CHANGES instructions for branching in git.
    
    We have this info in the wiki, but it should be here too.


 src/tools/RELEASE_CHANGES | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES
index b76fe1a02a3..fc11c099e41 100644
--- a/src/tools/RELEASE_CHANGES
+++ b/src/tools/RELEASE_CHANGES
@@ -62,6 +62,11 @@ Starting a New Development Cycle
 ================================
 
 * Create a branch in git for maintenance of the previous release
+	o on master branch, do:
+		git pull           # be sure you have the latest "master"
+		git push origin master:refs/heads/"new-branch-name"
+	  for example,
+		git push origin master:refs/heads/REL9_2_STABLE
 
 * Increment the major version number in src/tools/version_stamp.pl
 


[parent: 357c5493349c]