I want to setup a test-bed, but eventually, parellel development would be
30+ simultaneous streams needing to be merged back into the next release <
version-xx.x> branch.
parellel branches would need to be "rebased" (to borrow from clearcase
terminology) regulary from current release branch , as the <version-xx.x+1>
increments until <feature-y> branch goes out in <version-xx.x+N>
I haven't seen too much documentation on managing this yet for subversion.
Got any suggestions?
On 3/30/06, Lakshman Srilakshmanan <
lakshman.srilakshmanan@tradingpost.com.au> wrote:
>
> Hi Anthony,
>
> Our one and only reason to migrate from cvs/sourceSafe was to enable
> parallel development
>
> We have about 90 projects and 28 developers. 3 of the projects have
> between 3 and 5 streams of development. Others have generally 2. One for
> Support and one for Development.
> Our trunk mirrors production at all time.
>
> Thanks
> Lakshman
>
> -----Original Message-----
> From: ettinger@gmail.com [mailto:ettinger@gmail.com] On Behalf Of
> Anthony Ettinger
> Sent: Friday, 31 March 2006 3:10 PM
> To: users@subversion.tigris.org
> Subject: parellel development
>
> how well does svn support parellel development? it's been said that
> cvs isn't very good at it with respect to say clearcase.
>
>
>
> --
> Anthony Ettinger
> Signature: http://chovy.dyndns.org/hcard.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
Anthony Ettinger
Signature: http://chovy.dyndns.org/hcard.html
Received on Fri Mar 31 06:44:00 2006