Excerpts from Thierry Carrez's message of 2017-03-13 15:19:40 +0100: > Doug Hellmann wrote: > > Excerpts from Alex Schultz's message of 2017-03-09 11:29:28 -0700: > >> On Thu, Mar 9, 2017 at 10:54 AM, Doug Hellmann <d...@doughellmann.com> > >> wrote: > >>> Excerpts from Alex Schultz's message of 2017-03-07 12:56:17 -0700: > >>>> So what I'm proposing is to use a "-dev" pre-release identifier > >>>> between version releases for puppet modules. As part of the tagging > >>>> process we could propose the next release version with "-dev" to the > >>>> repository. The flow would look something like... > >>>> [...] > > As an aside, we used to do that for pre-versioned deliverables (drop the > "2015.1.0" as the "next" version in setup.cfg as the very first commit > in master after a branch point). The main issue with it was that it > required a lock on master to make it work (avoid other commits to make > it into master before the version bump).
It's not perfect, but since we can't make puppet take its version from the git tag (like we could with pbr), and the jobs would apply only to the puppet repositories, it seems like a reasonable approach. Doug __________________________________________________________________________ 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
