Tag Source For Release: Difference between revisions

From MediaWiki
Jump to navigationJump to search
No edit summary
(Updated with release and maintenance areas)
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.12.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''':


  [root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/2.12.0
  [root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/release/2.13.0
... output from branch creation ...
[root@nst-dev-32 repo]#
 
If you plan on changing the base operating system on the trunk after the release (for example moving from ''Fedora 13'' to ''CentOS 6''), you should also make a copy of the files under the ''maintenance'' area. For example:
 
 
[root@nst-dev-32 repo]# svn cp ${SVNROOT}/trunk ${SVNROOT}/maintenance/2.13.0
   
   
  ... output from branch creation ...
  ... output from branch creation ...
   
   
  [root@nst-dev-32 repo]#
  [root@nst-dev-32 repo]#

Revision as of 12:02, 22 September 2010

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:

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

... output from branch creation ...

[root@nst-dev-32 repo]#

If you plan on changing the base operating system on the trunk after the release (for example moving from Fedora 13 to CentOS 6), you should also make a copy of the files under the maintenance area. For example:


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

... output from branch creation ...

[root@nst-dev-32 repo]#