>> 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.
Actually, post/pre doesn't make a difference on stable branches. I tried locally on keystone stable/kilo and generated versions stay the same. * current pre-version setup i.e. version = 2015.1.2 in setup.cfg ** commit 070b51603879f0f70f85f72e9e82126d1bb398ba Bump stable/kilo next version to 2015.1.2 2015.1.2.dev1 ** review 205130 rebased on top of 070b516 Bump... 2015.1.2.dev2 * post-version i.e. version = line removed from setup.cfg on top of 070b516 Bump... commit fb9582acc739d7719da0f1cc5f29b9e24097e025 Author: Alan Pevec <[email protected]> Date: Thu Jul 30 12:07:27 2015 +0200 Switch to post-versioning Change-Id: Ie4758058672bdeff86147f796d53f602a65228f1 diff --git a/setup.cfg b/setup.cfg index e8d84e3..da0edb9 100644 --- a/setup.cfg +++ b/setup.cfg @@ -1,6 +1,5 @@ [metadata] name = keystone -version = 2015.1.2 summary = OpenStack Identity description-file = README.rst 2015.1.2.dev2 ** review 205130 rebased on top of Switch to post-versioning 2015.1.2.dev3 And when I tag that commit locally: $ git tag 2015.1.2 $ python ./setup.py --version 2015.1.2 Then one backport on top of that: 2015.1.3.dev1 So all is good and safe to remove version = lines from setup.cfg on stable branches. Cheers, Alan __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
