On 2015-11-24 14:34:19 +0100 (+0100), Alan Pevec wrote:
> > But to illustrate better the issue I'm seeing:
> > http://tarballs.openstack.org/cinder/cinder-stable-juno.tar.gz contains
> > a directory cinder-2014.2.4.dev24, which is kind of wrong. That's the
> > bit that I'd like to see fixed.
>
> T
> I've confirmed that the juno side of kilo grenade is not blowing up [1], but
> I'm not sure why it's not blowing up. Trying to figure that out.
It would blow up if something were merged after 2014.2.4 tag which
won't happen before version in setup.cfg is either bumped or removed
so we're safe :)
On 11/24/2015 10:42 AM, Matt Riedemann wrote:
On 11/23/2015 4:50 PM, Alan Pevec wrote:
2015-11-23 17:31 GMT+01:00 Matt Riedemann :
Or do you also suggest juno-eol != 2014.2.4?
I'd prefer to just remove the version tag in setup.cfg entirely so we
switch
to post-versioning, then we can EOL t
On 11/23/2015 4:50 PM, Alan Pevec wrote:
2015-11-23 17:31 GMT+01:00 Matt Riedemann :
Or do you also suggest juno-eol != 2014.2.4?
I'd prefer to just remove the version tag in setup.cfg entirely so we switch
to post-versioning, then we can EOL the thing. That's what we do internally
on EOL sta
> But to illustrate better the issue I'm seeing:
> http://tarballs.openstack.org/cinder/cinder-stable-juno.tar.gz contains
> a directory cinder-2014.2.4.dev24, which is kind of wrong. That's the
> bit that I'd like to see fixed.
That version was correct at the time tarball was generated, if it wer
Le lundi 23 novembre 2015, à 14:00 +0100, Ihar Hrachyshka a écrit :
> Vincent Untz wrote:
>
> >Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit :
> >>Vincent Untz wrote:
> >>
> >>>Hi,
> >>>
> >>>I know 2014.2.4 is (in theory) the last juno release, but I'd still
> >>>expect to s
2015-11-23 17:31 GMT+01:00 Matt Riedemann :
>> Or do you also suggest juno-eol != 2014.2.4?
> I'd prefer to just remove the version tag in setup.cfg entirely so we switch
> to post-versioning, then we can EOL the thing. That's what we do internally
> on EOL stable branches (switch to post-versionin
On 11/23/2015 7:00 AM, Ihar Hrachyshka wrote:
Vincent Untz wrote:
Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit :
Vincent Untz wrote:
Hi,
I know 2014.2.4 is (in theory) the last juno release, but I'd still
expect to see a post-release bump to 2014.2.5 in git, to avoi
Vincent Untz wrote:
Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit :
Vincent Untz wrote:
Hi,
I know 2014.2.4 is (in theory) the last juno release, but I'd still
expect to see a post-release bump to 2014.2.5 in git, to avoid any
confusion as to what lives in git. This is
Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit :
> Vincent Untz wrote:
>
> >Hi,
> >
> >I know 2014.2.4 is (in theory) the last juno release, but I'd still
> >expect to see a post-release bump to 2014.2.5 in git, to avoid any
> >confusion as to what lives in git. This is especia
Vincent Untz wrote:
Hi,
I know 2014.2.4 is (in theory) the last juno release, but I'd still
expect to see a post-release bump to 2014.2.5 in git, to avoid any
confusion as to what lives in git. This is especially useful if people
build new tarballs from git.
Any objection against this, before
Hi,
I know 2014.2.4 is (in theory) the last juno release, but I'd still
expect to see a post-release bump to 2014.2.5 in git, to avoid any
confusion as to what lives in git. This is especially useful if people
build new tarballs from git.
Any objection against this, before I send patches? :-)
Ch
12 matches
Mail list logo
