New Post: Cumulative and non cumulative hotfixes

I suggest you look at the "Branching and Merging Guide.pdf" in the download and closely study the Standard and Advanced plans. It sounds as if one of them would serve you well. Keep in mind that you can usually change your branching strategy if it does not work for you. You can also try them out in a sandbox if you are really nervous.

On Fri, Sep 7, 2012 at 1:25 PM, msauvaget <notifications@codeplex.com> wrote:

From: msauvaget

Thanks for your help and I'll try to explain the best I can our process. First of all our branch design is quite theoretical at the moment.

Then yes, every hotfix is RI in the "Patch" branch in its current version (we may have 4 or 5 patch version of a major). When I make a hotfix I can only branch "Patch" from the version to fix. Let say 5.2.3.1 is a hotfix of 5.2.3.0 (this is our non-standard way of versionning), this fix is then RI in "Patch" (which can be in developpement for 5.2.4.0 or further). I'd like to be able to make other fixes with changes of 5.2.3.1 but I can't branch "Patch" from its latest version for obvious reasons.

Our project is based on ASP .NET web forms and consists of several DLL and other ressources. We aren't always sending a complete new setup of the software but it may happen for easy replacement.

Read the full discussion online.

To add a post to this discussion, reply to this email (vsarbranchingguide@discussions.codeplex.com)

To start a new discussion for this project, email vsarbranchingguide@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

David Kreth Allen

612-374-1119