On 8/12/2009 17:58, Donovan Bray wrote: > I used to do that, but we adopted a different workflow that made > master our stable production branch. > > We now have three primary branches, master, rc, and testing. Topic > branches are rebased and merged into testing, and that's where all of > the development happens. When testing is stable and potentially > releasable it's merged into rc where it's qa'd, once it meets qa > approval it's merged into master. We use tags only to document when > the merges were approved. We deploy based on the branch. > > This has worked well and kept our continuous integration fairly simple. > I actually thought of this inspired by capistrano-ext multistage. By doing this I wouldn't even need to prompt for the name of the tag, because the branch name would be in the stage config file.
I'll sleep a little on this idea. We were going to have separate development branches in the repository anyway. Thanks for the insight Donovan. Greatly appreciated. -- Ionut G. Stan I'm under construction | http://blog.igstan.ro/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
