Difference between revisions of "Tag Source For Release"

From NST Wiki
Jump to navigationJump to search
Line 1: Line 1:
Use the ''svn cp'' command to create a branch of the files used for the release (a copy of "trunk"). For example, if creating release '''2.13.0''':
+
Use the ''svn cp'' command to create a branch of the files used for the release (a copy of "trunk"). For example, if creating release '''2.13.0''' for subversion revision ''1702'':
  
  [root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/releases/2.13.0
+
  [root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/releases/2.13.0-1702
 
... output from branch creation ...
 
 
[root@nst-dev-32 repo]#
 
 
 
If you are creating a maintenance release (a new ISO to include updated packages so people won't need to ''yum update'' so many files), you should make a copy of the files under the ''maintenance'' area. For example (the 1720 represents the subversion revision when the ISO was created):
 
 
 
[root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/maintenance/2.13.0-1702
 
 
   
 
   
 
  ... output from branch creation ...
 
  ... output from branch creation ...
 
   
 
   
 
  [root@nst-dev-32 repo]#
 
  [root@nst-dev-32 repo]#

Revision as of 15:22, 20 January 2011

Use the svn cp command to create a branch of the files used for the release (a copy of "trunk"). For example, if creating release 2.13.0 for subversion revision 1702:

[root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/releases/2.13.0-1702

... output from branch creation ...

[root@nst-dev-32 repo]#