Alan Pevec wrote: >> I think pushing them up earlier would indeed make it easier for folk. > > Indeed, but it's too late now. > >> But its not as good as using post-versioniing :) > > Agreed, after 2015.1.2 version bumps are merged, I'll propose version= > line removals on stable branches so this situation doesn't happen > again.
Err, no. Post-versioning means all projects use semantic rather than date-based version numbers, which happens starting with *liberty*. Remaining kilo and juno stable releases will still need to use pre-versioning. The way we did it in the past was to push the setup.cfg version=2015.1.2 bump BEFORE we tag, then once that is merged, tag the previous commit in history as 2015.1.1. That way you avoid the lockstep (and ensure no intermediary badly-versioned tarball can be produced). Any reason why that wouldn't work anymore ? -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
