search for: r1635

...008 > New Revision: 1631 > > Log: > Create an 'experimental' branch for changes that should > not be in the next stable release One potential problem with this is that it is easy for the branches to get out of sync with each other (some changes, e.g. the packaging removal in r1635, should be applied to both branches). I have used svnmerge.py at work for several months now, and it seems to be a decent way to keep several branches in sync (without forcing everyone to upgrade to Subversion 1.5, or switching to another SCM). Info: http://www.orcaware.com/svn/wiki/Svnmerge.py...