On Mon, 2006-11-13 at 05:19, Gundersen, Richard wrote:
> I just thought of another argument for feature branching…
>
>
>
> One of the arguments against, is that all these branches are difficult
> to keep track of.
>
> Say you have ten systems (not unusual), all at different stages of
> their life. Operations (or someone who isn’t necessarily too familiar
> with the details of each system) have to release one of them after a
> mainenance weekend.
>
> With the release strategy, they have a small forest of release
> branches to choose from. Hopefully someone will have told them which
> branch is the current production branch, or that they have been given
> obvious looking names. Or a list is maintained somewhere.
I'd expect a tag for release regardless of whether the source
is the trunk or a branch - and operations shouldn't release
anything unless someone gives them the correct tag. Some
places would have some QA testing before the tag is made.
On the other side of things, how do multiple developers
update to see each others work if they are putting all
their new changes into separate branches? If you do most
common work on the trunk and only branch near release
this becomes very easy, and hopefully the changes made
after that point will be small and specific to that version.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 14 03:46:48 2006