On 11/23/2015 4:50 PM, Alan Pevec wrote:
2015-11-23 17:31 GMT+01:00 Matt Riedemann <[email protected]>:
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-versioning since we have our own
release cycles). And I'd be OK with this just to keep stable/kilo moving
until juno is EOL'ed.
Where is stable/kilo blocked because of this?? There shouldn't be
anything merged after 2014.2.4 tag
i.e. juno-eol == 2014.2.4
Cheers,
Alan
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I thought we'd be hitting this kind of issue [1] on stable/kilo changes
that run grenade where the old side is juno, and I though pbr would blow
up installing those, but so far I haven't seen any job failures like
that to indicate it's a problem.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-October/076928.html
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
