On 2015-04-16 2:10 PM, Richard Raseley wrote: > > I am certainly sympathetic to your situation - having the world change > beneath your feet is never a good place to be. =] > > It does seem, however, that there is a disconnect between your > expectations (as I understand them) of what the 'master' branch > represents, and what it has traditionally represented - the 'bleeding edge' > > Master is volatile - it is expected to be volatile. As the code > progresses between releases it is expected that things can (and will) > break. > > The solution, in my mind, is not to redefine what it means to be master, > but rather to be more aggressive about back-porting changes to stable > branches. > > I am very much in favor of discussions that include your proposed > solution above (i.e. 'current-1' support), as long as it is identified > as a transitional step; I do pretty strongly believe that the right > long-term model is to treat master as the 'bleeding edge' and to only > pin yourself to stable releases. >
Should I be in the same situation as Matt Fischer (using master to install Juno), I would use this solution: https://github.com/michaeltchapman/puppet-openstacklib/blob/master/manifests/compat/nova.pp -- Mathieu __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev