On Tue, Mar 18, 2014 at 5:30 PM, Monty Taylor 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,
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
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.
On Tue, 2014-03-18 at 09:55 +1300, Robert Collins wrote:
> On 18 March 2014 07:28, Jay Pipes wrote:
> > On Mon, 2014-03-17 at 16:10 +1300, Robert Collins wrote:
>
> > Hi Rob, thanks for the heads up.
> >
> > A number of us use pbr for outside-of-OpenStack projects, and have
> > relied on it for t
On 18 March 2014 09:32, Doug Hellmann wrote:
> As mordred, lifeless, and I discussed in #openstack-infra today, this
> represents a backwards-incompatible change to the version format strings,
> which we believe are being consumed by packagers. We should wait until after
> the feature freeze, mak
On 18 March 2014 07:28, Jay Pipes wrote:
> On Mon, 2014-03-17 at 16:10 +1300, Robert Collins wrote:
> 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.
Yup!
> I'm a lit
On Sun, Mar 16, 2014 at 11:10 PM, 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-postver
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-postve
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 versio
