RE: Branching strategy - Feature vs Release

On Mon, 2006-11-13 at 05:03, Gundersen, Richard wrote:

> The big benefit of keeping X and Y on their own branches, is when you
> want to release X but NOT Y (maybe Y isn’t finished yet, or Y can only
> be released on a certain date for some legal requirement or other
> constraint).

I don't see how that's an advantage for developing on
branches as compared to developing on the trunk and branching
X near it's release with a later branch for Y.

> Yes, I like to assume that I have multiple customers. This doesn’t
> mean multiple running versions though. In most large systems I have
> worked on, there are different groups of users. Perhaps they are in
> different countries, and therefore have different laws. Or, different
> divisions with differing requirements. But they all use the SAME
> system. (The alternative would be to give them all their own copies of
> the system, but I wouldn’t like to maintain that!)

Depending on the nature of the system, you'll likely eventually
run into a situation where one or more customers can't or
won't upgrade at the same time as the others and then
find a bug you have to fix in their older version. If you
branched for the release, you already have a place to do
this work.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org