On 2017-03-09 12:12:01 +0100 (+0100), Alan Pevec wrote: > 2017-03-09 10:41 GMT+01:00 Alfredo Moralejo Alonso <[email protected]>: > > On Wed, Mar 8, 2017 at 12:44 PM, Steven Hardy <[email protected]> wrote: > >> https://bugs.launchpad.net/tripleo/+bug/1669462 > >> > >> I'm not clear on the best path forward at this point, but the simplest one > >> suggested so far is to simply tag a new pre-milestone/alpha release for all > >> master branches, which will enable testing upgrades to master. > > That would be indeed simplest and cleanest solution but it has been > rejected in the past, IIUC with reasoning that projects are not sure > what will be their next version. IMHO that should not be the case if > the project has decided to have a stable branch and follows semver and > stable branch policy: in that case project will keep X.Y frozen on > stable so master should be bumped to at least X.Y+1 immediately after > branching stable. [...]
In the past we addressed this by automatically merging the release tag back into master, but we stopped doing that a cycle ago because it complicated release note generation. -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
