RE: Branching strategy - Feature vs Release

> 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.

>>>> Why should you have to wait until X is finished and branched, ready for its release, before you start development on Y? You might want to start development for both X and Y at the same time.

> 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.

>>>>>>> I think I underand now. Are you talking about software that's going to get shipped out to customers? I'm talking from the point of view of a web-based system, where they all access the same instance of system. My changes are all on a branch too. The change only gets released when its ready, so while it's on the branch I can mess around with it as much as I want. Customers will not refuse to use the system, because the trunk only ever contains code that has been accepted by the customer. Sorry, I should have stated that originally.

-- 
  Les Mikesell
   lesmikesell@gmail.com
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
*** Disclaimer *** 
This electronic communication is confidential and for the exclusive use of the addressee. It may contain private and confidential information. The information, attachments and opinions contained in this E-mail are those of its author only and do not necessarily represent those of London Scottish Bank PLC or any other members of the London Scottish Group. 
If you are not the intended addressee, you are prohibited from any disclosure, distribution or further copying or use of this communication or the information in it or taking any action in reliance on it. If you have received this communication in error please notify the Information Security Manager at ISM@London-Scottish.com as soon as possible and delete the message from all places in your computer where it is stored. 
We utilise virus scanning software but we cannot guarantee the security of electronic communications and you are advised to check any attachments for viruses. We do not accept liability for any loss resulting from any corruption or alteration of data or importation of any virus as a result of receiving this electronic communication. 
Replies to this E-mail may be monitored for operational or business reasons. London Scottish Bank PLC is regulated by the Financial Services Authority.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org