+1 It seems to be the common practice in the DVCS community and I don't see a reason not to.
On Mon, Aug 10, 2009 at 3:16 PM, James Turnbull <[email protected]>wrote: > Hi all > > I just wanted to query consider its getting close how we planned to > manage Git after 0.25.0. My plan (and obviously open to input and Luke > has a different view, etc, etc, :)) was: > > Branch master to 0.25.x. The 0.25.x branch continue on as the home for > fixes for the 0.25.x releases - .1, .2, etc. The master branch would > remain "development" as such and would be targeted at 0.26.0. > > We would merge in fixes back and forth when required from master and > 0.25.x. > > Thoughts? Doctrinal arguments? > > James > > -- > Author of: > * Pro Linux Systems Administration > (http://tinyurl.com/linuxadmin) > * Pulling Strings with Puppet > (http://tinyurl.com/pupbook) > * Pro Nagios 2.0 > (http://tinyurl.com/pronagios) > * Hardening Linux > (http://tinyurl.com/hardeninglinux) > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
