Re: [openstack-dev] [goals][python3][heat][stable] how should we proceed with ocata branch
On 10/3/2018 11:21 AM, Zane Bitter wrote: That patch is the only thing blocking the cleanup patch in project-config, so I would like to get a definitive answer about what to do. Should we close the branch, or does someone want to try to fix things up? I think we agreed on closing the branch, and Rico was looking into the procedure for how to actually do that. Doug [1]https://review.openstack.org/#/c/597272/ I'm assuming heat-agents is a service, not a library, since it doesn't show up in upper-constraints. It's a guest agent, so neither :) Based on that, does heat itself plan on putting its stable/ocata branch into extended maintenance mode and if Wearing my Red Hat hat, I would be happy to EOL it. But wearing my upstream hat, I'm happy to keep maintaining it, and I was not proposing that we EOL heat's stable/ocata as well. so, does that mean EOLing the heat-agents stable/ocata branch could cause problems for the heat stable/ocata branch? In other words, will it be reasonable to run CI for stable/ocata heat changes against a heat-agents ocata-eol tag? I don't think that's a problem. The guest agents rarely change, and I don't think there's ever been a patch backported by 4 releases. OK, cool, sounds like killing the heat-agent ocata branch is the thing to do then. -- Thanks, Matt __ 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] [goals][python3][heat][stable] how should we proceed with ocata branch
Zane Bitter writes: > On 3/10/18 9:42 AM, Matt Riedemann wrote: >> On 10/3/2018 7:58 AM, Doug Hellmann wrote: >>> There is one more patch to import the zuul configuration for the >>> heat-agents repository's stable/ocata branch. That branch is apparently >>> broken, and Zane suggested on the review [1] that we abandon the patch >>> and close the branch. >>> >>> That patch is the only thing blocking the cleanup patch in >>> project-config, so I would like to get a definitive answer about what to >>> do. Should we close the branch, or does someone want to try to fix >>> things up? > > I think we agreed on closing the branch, and Rico was looking into the > procedure for how to actually do that. OK. I am going to abandon the patch to import the zuul settings then. Abandoning all open patches is one of the early steps anyway, and doing that now for this 1 patch will allow us to proceed with the cleanup. Doug __ 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] [goals][python3][heat][stable] how should we proceed with ocata branch
On 3/10/18 9:42 AM, Matt Riedemann wrote: On 10/3/2018 7:58 AM, Doug Hellmann wrote: There is one more patch to import the zuul configuration for the heat-agents repository's stable/ocata branch. That branch is apparently broken, and Zane suggested on the review [1] that we abandon the patch and close the branch. That patch is the only thing blocking the cleanup patch in project-config, so I would like to get a definitive answer about what to do. Should we close the branch, or does someone want to try to fix things up? I think we agreed on closing the branch, and Rico was looking into the procedure for how to actually do that. Doug [1]https://review.openstack.org/#/c/597272/ I'm assuming heat-agents is a service, not a library, since it doesn't show up in upper-constraints. It's a guest agent, so neither :) Based on that, does heat itself plan on putting its stable/ocata branch into extended maintenance mode and if Wearing my Red Hat hat, I would be happy to EOL it. But wearing my upstream hat, I'm happy to keep maintaining it, and I was not proposing that we EOL heat's stable/ocata as well. so, does that mean EOLing the heat-agents stable/ocata branch could cause problems for the heat stable/ocata branch? In other words, will it be reasonable to run CI for stable/ocata heat changes against a heat-agents ocata-eol tag? I don't think that's a problem. The guest agents rarely change, and I don't think there's ever been a patch backported by 4 releases. cheers, Zane. __ 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] [goals][python3][heat][stable] how should we proceed with ocata branch
On 10/3/2018 7:58 AM, Doug Hellmann wrote: There is one more patch to import the zuul configuration for the heat-agents repository's stable/ocata branch. That branch is apparently broken, and Zane suggested on the review [1] that we abandon the patch and close the branch. That patch is the only thing blocking the cleanup patch in project-config, so I would like to get a definitive answer about what to do. Should we close the branch, or does someone want to try to fix things up? Doug [1]https://review.openstack.org/#/c/597272/ I'm assuming heat-agents is a service, not a library, since it doesn't show up in upper-constraints. Based on that, does heat itself plan on putting its stable/ocata branch into extended maintenance mode and if so, does that mean EOLing the heat-agents stable/ocata branch could cause problems for the heat stable/ocata branch? In other words, will it be reasonable to run CI for stable/ocata heat changes against a heat-agents ocata-eol tag? -- Thanks, Matt __ 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-dev] [goals][python3][heat][stable] how should we proceed with ocata branch
There is one more patch to import the zuul configuration for the heat-agents repository's stable/ocata branch. That branch is apparently broken, and Zane suggested on the review [1] that we abandon the patch and close the branch. That patch is the only thing blocking the cleanup patch in project-config, so I would like to get a definitive answer about what to do. Should we close the branch, or does someone want to try to fix things up? Doug [1] https://review.openstack.org/#/c/597272/ __ 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
