Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-17 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2015-06-16 15:55:04 -0400: Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: Doug Hellmann wrote: [...] I put together a little script [1] to try to count the previous releases for projects, to use that as the basis for their

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Doug Hellmann
Excerpts from Timur Nurlygayanov's message of 2015-06-16 12:49:02 +0300: Hi Doug, I suggest to use some version for neutron-*aas plugins, probably, 1.0.0 just to have one pattern for all components. If we will not use numbers for the first releases (or release candidates) it will be hard to

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Doug Hellmann
Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: Doug Hellmann wrote: [...] I put together a little script [1] to try to count the previous releases for projects, to use that as the basis for their first SemVer-based version number. I pasted the output into an etherpad

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Thierry Carrez
Doug Hellmann wrote: Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: We also traditionally managed the previously-incubated projects. That would add the following to the mix: barbican 1.0.0 designate 1.0.0 manila 1.0.0 zaqar 1.0.0 Those didn't have the

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Doug Hellmann
Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: Doug Hellmann wrote: [...] I put together a little script [1] to try to count the previous releases for projects, to use that as the basis for their first SemVer-based version number. I pasted the output into an etherpad

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Thierry Carrez
Doug Hellmann wrote: [...] I still need to chat with Kyle about some of the neutron spin-out projects, since their repositories have the old neutron tags but I don't think it's appropriate to use the same version number as neutron for newer projects. [...] neutron 8.0.0 neutron-fwaas

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Sergey Lukjanov
I have a question regarding proposed release versions - are we starting to count releases from zero? And 2015.1 (Kilo) missed in all projects in etherpad. So, it means if we're starting from 0.0.0 then the proposed versions are correct, but if we want to start from 1.0.0 (IMO it's better), we

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/16/2015 09:44 AM, Thierry Carrez wrote: Doug Hellmann wrote: [...] I still need to chat with Kyle about some of the neutron spin-out projects, since their repositories have the old neutron tags but I don't think it's appropriate to use the

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Thierry Carrez
Doug Hellmann wrote: [...] I put together a little script [1] to try to count the previous releases for projects, to use that as the basis for their first SemVer-based version number. I pasted the output into an etherpad [2] and started making notes about proposed release numbers at the top.

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Sergey Lukjanov
Agree with Thierry, IMO it sounds more consistent On Tue, Jun 16, 2015 at 12:45 PM, Thierry Carrez thie...@openstack.org wrote: Doug Hellmann wrote: [...] I put together a little script [1] to try to count the previous releases for projects, to use that as the basis for their first

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-16 Thread Timur Nurlygayanov
Hi Doug, I suggest to use some version for neutron-*aas plugins, probably, 1.0.0 just to have one pattern for all components. If we will not use numbers for the first releases (or release candidates) it will be hard to understand what the version it is. What do you think about it? Thank you! On

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-15 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2015-06-05 10:23:52 -0400: Excerpts from Doug Hellmann's message of 2015-05-29 17:38:04 -0400: This message is a summary of the notes from the “Release Versioning Servers” discussion held during the release management/QA/infrastructure meetup

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-05 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2015-05-29 17:38:04 -0400: This message is a summary of the notes from the “Release Versioning Servers” discussion held during the release management/QA/infrastructure meetup period on Friday morning at the summit, along with some commentary I thought

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread John Garbutt
On 29 May 2015 at 22:38, Doug Hellmann d...@doughellmann.com wrote: As with our other semver projects, we will use pbr’s interpretation of the semver rules (http://docs.openstack.org/developer/pbr/semver.html) for minor updates and patch releases. I don’t believe we discussed whether to

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread Doug Hellmann
Excerpts from John Garbutt's message of 2015-06-01 12:26:48 +0100: On 29 May 2015 at 22:38, Doug Hellmann d...@doughellmann.com wrote: As with our other semver projects, we will use pbr’s interpretation of the semver rules (http://docs.openstack.org/developer/pbr/semver.html) for minor

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread Doug Hellmann
Excerpts from Thierry Carrez's message of 2015-06-01 10:30:33 +0200: Doug Hellmann wrote: Please let me know if you think I missed any details, or misunderstood something as agreed to. Or, of course, if you weren’t there and see something wrong with the plan after looking at it now.

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread Thierry Carrez
Doug Hellmann wrote: Please let me know if you think I missed any details, or misunderstood something as agreed to. Or, of course, if you weren’t there and see something wrong with the plan after looking at it now. We'd also provide a tool to easily translate the series name with the current

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread Jeremy Stanley
On 2015-06-01 08:53:41 -0400 (-0400), Doug Hellmann wrote: [...] pbr generates versions like x.y.z.postN on each commit now, indicating N commits since the x.y.z tag. So I think we're OK with version numbers without having to do any tagging explicitly. [...] Well, technically x.y.(z+1).devN

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread Thierry Carrez
Doug Hellmann wrote: Excerpts from Thierry Carrez's message of 2015-06-01 10:30:33 +0200: Doug Hellmann wrote: Please let me know if you think I missed any details, or misunderstood something as agreed to. Or, of course, if you weren’t there and see something wrong with the plan after

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-06-01 Thread Donald Stufft
On June 1, 2015 at 1:03:08 PM, Jeremy Stanley (fu...@yuggoth.org) wrote: Since pip treats .postN in strange ways, it's not entirely safe to rely on the old PBR behavior which would have made this 2.25.0.post8. In particular, if we were to ever upload that to PyPI (terrible idea I know,

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-05-29 Thread Jeremy Stanley
On 2015-05-29 17:38:04 -0400 (-0400), Doug Hellmann wrote: [...] This will result in resetting the version numbers to values lower than they are currently (12 2015), but the distributions can prepend an epoch value to their version number to ensure upgrades work properly. [...] Also for

[openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

2015-05-29 Thread Doug Hellmann
This message is a summary of the notes from the “Release Versioning Servers” discussion held during the release management/QA/infrastructure meetup period on Friday morning at the summit, along with some commentary I thought of as I was typing them up. There is no etherpad for that session, but