RE: Branched and non-branched work flows?
From: Bob Archer <bob.archer_at_amsi.com>
Date: Mon, 1 Jun 2009 15:11:57 -0400
> Here's how we do it:
That's pretty close to how we do it to. But, we build, test and release from trunk. We don't allow v+1 to be checked into trunk until the release is gold. (If there is need we create a temp branch for v+1, but this doesn't happen often.)
Once we release we tag the release and also create a branch from the just release product. That branch is used for fixes to that release. The fixes are checked into the branch and merged into trunk and the fixes to the branch release are built from the branch.
The biggest pain for us right now is setting up CI on our branches. But I am in the process of making our build scripts smarter and using relative pathing so that getting a build running on a branch is no more difficult than modifying the svn path in the ccnet.config file that is in the branch and adding an include to the main ccnet.config file pointing to that new branch wc.
BOb
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.