Re: [openstack-dev] Targeting icehouse-eol?
let's release this last one (codename: Farewell ?) point release. I can do this next week after we finish pending reviews. Remaining stable/icehouse reviews[1] have -2 or -1 except https://review.openstack.org/176019 which I've asked neutron-stable-maint to review. Matt, anything else before we can tag 2014.1.5 and icehouse-eol ? Cheers, Alan [1] https://review.openstack.org/#/q/status:open+AND+branch:stable/icehouse+AND+%28project:openstack/nova+OR+project:openstack/keystone+OR+project:openstack/glance+OR+project:openstack/cinder+OR+project:openstack/neutron+OR+project:openstack/horizon+OR+project:openstack/heat+OR+project:openstack/ceilometer+OR+project:openstack/trove%29,n,z __ 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
Re: [openstack-dev] Targeting icehouse-eol?
The only open question I have is if we need to do an Icehouse point release prior to the tag and dropping the branch, but I don't think that's happened in the past with branch end of life - the eol tag basically serves as the placeholder to the last 'release'. I don't think we need to do a point release, there will be the icehouse-eol tag which will mark the same thing. But, even if we later decide to add a point release to mark the same thing it is trivial to push another tag for the same sha1. I CC-ed the stable branch release managers for their opinion on it. We definitely announced a 2014.1.5 last icehouse release, so I think we should probably do one. Ideally we would have time to coordinate it in the coming week so that both plans are compatible. Based on previoius 15 months plan, 2014.1.5 was targeting July 2015, so releasing it next week would be close enough: https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Ficehouse_releases I'm not sure if release machinery would work after removing the branch so let's release this last one (codename: Farewell ?) point release. I can do this next week after we finish pending reviews. Cheers, Alan __ 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
Re: [openstack-dev] Targeting icehouse-eol?
Matthew Treinish wrote: On Wed, Jun 03, 2015 at 09:06:29AM -0500, Matt Riedemann wrote: Following on the thread about no longer doing stable point releases [1] at the summit we talked about doing icehouse-eol pretty soon [2]. I scrubbed the open stable/icehouse patches last week and we're down to at least one screen of changes now [3]. My thinking was once we've processed that list, i.e. either approved what we're going to approve or -2 what we aren't, then we should proceed with doing the icehouse-eol tag and deleting the branch. Is everyone generally in agreement with doing this soon? If so, then I'm thinking target a week from today for the stable maint core team to scrub the list of open reviews in the next week and we then get the infra team to tag the branch and close it out. Not really a surprise, but I support doing this soon. Next week seems fine to me. Right, I also support doing this sometimes this month. The only open question I have is if we need to do an Icehouse point release prior to the tag and dropping the branch, but I don't think that's happened in the past with branch end of life - the eol tag basically serves as the placeholder to the last 'release'. I don't think we need to do a point release, there will be the icehouse-eol tag which will mark the same thing. But, even if we later decide to add a point release to mark the same thing it is trivial to push another tag for the same sha1. I CC-ed the stable branch release managers for their opinion on it. We definitely announced a 2014.1.5 last icehouse release, so I think we should probably do one. Ideally we would have time to coordinate it in the coming week so that both plans are compatible. -- Thierry Carrez (ttx) signature.asc Description: OpenPGP digital signature __ 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
Re: [openstack-dev] Targeting icehouse-eol?
On Wed, Jun 03, 2015 at 09:06:29AM -0500, Matt Riedemann wrote: Following on the thread about no longer doing stable point releases [1] at the summit we talked about doing icehouse-eol pretty soon [2]. I scrubbed the open stable/icehouse patches last week and we're down to at least one screen of changes now [3]. My thinking was once we've processed that list, i.e. either approved what we're going to approve or -2 what we aren't, then we should proceed with doing the icehouse-eol tag and deleting the branch. Is everyone generally in agreement with doing this soon? If so, then I'm thinking target a week from today for the stable maint core team to scrub the list of open reviews in the next week and we then get the infra team to tag the branch and close it out. Not really a surprise, but I support doing this soon. Next week seems fine to me. The only open question I have is if we need to do an Icehouse point release prior to the tag and dropping the branch, but I don't think that's happened in the past with branch end of life - the eol tag basically serves as the placeholder to the last 'release'. I don't think we need to do a point release, there will be the icehouse-eol tag which will mark the same thing. But, even if we later decide to add a point release to mark the same thing it is trivial to push another tag for the same sha1. [1] http://lists.openstack.org/pipermail/openstack-dev/2015-May/065144.html [2] https://etherpad.openstack.org/p/YVR-relmgt-stable-branch [3] https://review.openstack.org/#/q/status:open+branch:stable/icehouse,n,z -Matt Treinish pgp0XpfsPKAOn.pgp Description: PGP signature __ 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
