Please note:The SCons wiki is now restored from the attack in March 2013. All old passwords have been invalidated. Please reset your password if you have an account. If you note missing pages, please report them to webmaster@scons.org. Also, new account creation is currently disabled due to an ongoing spam flood (2013/08/27).

These instructions use outdated workflow based on svnmerge tool.

This flow sets up a branch for a potential series of point releases.

FIXME:

Initialize...
  $ export SVN=http://scons.tigris.org/svn/scons
  $ export POINT=3.2.x

Create point branch...
  $ cd my_working_directory
  $ svn co $SVN/trunk
  $ svn cp trunk $SVN/branches/$POINT
  $ svn commit -m'Added branches/$POINT based on trunk' trunk
I don't know why that last line is needed...

Set svnmerge base...
  $ svn co $SVN/branches/$POINT working
  $ (cd working && svnmerge init ../trunk)
  $ (cd trunk && svnmerge init ../working)
  $ (cd working && svn commit -m'Set svnmerge base for $POINT')
  $ (cd trunk && svn commit -m'Set svnmerge base for trunk')

You can actually do both the "svnmerge init" and "svn commit" on one branch (in one directory) and then do both on the other branch, but doing it this way makes both of them end up with the same base revision number in the svnmerge property, which is nice and symmetric.

ReleaseHOWTO/NonTipSetupBody (last edited 2011-06-12 20:52:21 by mm-127-247-57-86)