On 9 June 2015 at 03:48, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2015-06-08 10:54:32 +1200 (+1200), Robert Collins wrote: >> On 8 June 2015 at 10:14, Alan Pevec <ape...@gmail.com> wrote: >> > 2015-06-06 19:08 GMT+02:00 Ian Cordasco <ian.corda...@rackspace.com>: >> >> Not exactly. PBR/OpenStack follow SemVer and 2015.1.0.38 isn't valid >> >> SemVer (http://semver.org/) >> > >> > Right, so semver compatible versioning on stable/kilo would be 2015.1.N >> > but PBR doesn't support that. >> >> PBR supports it fine. Whats the issue? > > Having PBR automatically increment the N in 2015.1.N for each patch > applied on the branch rather than needing it to be tagged.
I don't think pbr needs to do that to have the proposal work. We could tag from cron and use the actual tag pipeline to do release related stuff. E.g. its layer conflation to have pbr start assuming that untagged code isn't a release. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ 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
