On 11/20/2015 6:43 AM, Sean Dague wrote:
On 11/19/2015 08:56 PM, Rochelle Grober wrote:
Again, my plea to leave the Juno repository on git.openstack.org, but locked down
to enable at least grenade testing for Juno->Kilo upgrades. For upgrade
testing purposes, python2.6 is not needed as any
On 11/19/2015 08:56 PM, Rochelle Grober wrote:
> Again, my plea to leave the Juno repository on git.openstack.org, but locked
> down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade
> testing purposes, python2.6 is not needed as any cloud would have to upgrade
> python be
2015-11-20 3:22 GMT+01:00 Davanum Srinivas :
> fyi https://review.openstack.org/#/c/247677/
That's not the right answer to Rochelle's plea :)
It was actually already answered by Matt, with a suggestion that
_Kilo_ grenade job could simply checkout 2014.2.4 tag instead of
stable/juno and for that w
fyi https://review.openstack.org/#/c/247677/
On Thu, Nov 19, 2015 at 8:56 PM, Rochelle Grober
wrote:
> Again, my plea to leave the Juno repository on git.openstack.org, but locked
> down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade
> testing purposes, python2.6 is no
Again, my plea to leave the Juno repository on git.openstack.org, but locked
down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade
testing purposes, python2.6 is not needed as any cloud would have to upgrade
python before upgrading to kilo. The testing could/should be li
