> -----Original Message----- > From: Alan Pevec [mailto:ape...@gmail.com] > Sent: Friday, November 20, 2015 10:46 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [stable][infra][qa] Preparing 2014.2.4 (Juno) > WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer. > > > So we were brainstorming this with Rocky the other night. Would this be > possible to do by following: > > 1) we still tag juno EOL in few days time > > 2) we do not remove the stable/juno branch > > Why not? > > > 3) we run periodic grenade jobs for kilo > > From a quick look, grenade should work with a juno-eol tag instead of > stable/juno, it's just a git reference. > "Zombie" Juno->Kilo grenade job would need to set > BASE_DEVSTACK_BRANCH=juno-eol and for devstack all > $PROJECT_BRANCH=juno-eol (or 2014.2.4 should be the same commit). > Maybe I'm missing some corner case in devstack where stable/* is assumed > but if so that should be fixed anyway. > Leaving branch around is a bad message, it implies there support for it, while > there is not. > > Cheers, > Alan
That sounds like an easy compromise. - Erno > > __________________________________________________________ > ________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev