Open Stack

On Mon, 2014-03-17 at 16:10 +1300, Robert Collins wrote:
> Right now PBR's creation of versions for postversioning is problematic
> - it generates versions that (if recognized by pip) would be treated
> as releases, even when its a non-tagged commit.
> 
> https://etherpad.openstack.org/p/pbr-postversion-semver
> 
> The tl;dr is a proposal to generate dev marked versions of the lowest
> possible higher tag that we would accept - which would be any of full
> release or alpha/beta/rc
> 
> A related but can be done separately change is to pick version strings
> for alpha releases that are compatible with both PEP 440 and semver.
> 
> Feedback solicited - if this is something contentious, we can make it
> an opt-in feature, but it seems unambiguously better to the folk that
> chatted through it on #openstack-infra, so ideally I'd like to
> transition any existing incompatible tags we have, and then land code
> to make this the behaviour for post-versioned (the default - no
> 'version' key in setup.cfg) untagged commits.

Hi Rob, thanks for the heads up.

A number of us use pbr for outside-of-OpenStack projects, and have
relied on it for things like proper package versioning using git tags.

I'm a little unclear what, if any, changes to my standard python sdist
and upload actions I will need to take to publish releases of my
projects that use pbr.

Would you mind easing my mind and letting me know if this is something
that is going to break things for me? I'm no packaging expert, and rely
on things like pbr to do a lot of this magic for me :)

All the best,
-jay