[openstack-dev] Automatic version creation in PBR

Doug Hellmann doug.hellmann at dreamhost.com
Wed Mar 19 13:52:26 UTC 2014

On Tue, Mar 18, 2014 at 5:30 PM, Monty Taylor <mordred at inaugust.com> wrote:

> On 03/18/2014 04:25 AM, Thierry Carrez wrote:
>> Robert Collins wrote:
>>> If you set 'version' in setup.cfg, pbr's behaviour will not change at
>>> all.
>>> If you do not set 'version' in setup.cfg then:
>>>   - for tagged commits, pbr's behaviour will not change at all.
>>>   - for untagged commits, pbr will change from
>>> '$last_tag_version.$commit_count.g$sha' to
>>> '$next_highest_pre_release.dev$commit_count.g$sha'
>> That sounds sane to me. IIUC it shouldn't impact the release team. The
>> version number ends up being quite ugly, but in that precise case
>> prettiness is not a primary goal.
>> It may impact packagers in some corner cases so I'd engage with them to
>> check (#openstack-packaging ?) *and*, like Doug recommends, wait for
>> after icehouse release to make the change.
> We've also discussed adding a utility to transform the newer uglier but
> more pep440 correct generated version string into debian format for folks -
> since it is possible to do it purely mechanically, but grokking it totally
> might not be something someone wants to do.

I've created a blueprint to do this, but as I don't know the details of
the version numbers it doesn't have much detail. I would appreciate it if
anyone who does understand those differences would add some notes to 


> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140319/18aad49f/attachment.html>

More information about the OpenStack-dev mailing list