---- On Fri, 17 May 2024 08:27:12 -0700 Dmitriy Rabotyagov wrote ---
Just for projects to be aware - since these are now removed from Zuul project list, all projects who still had them in their required-projects for Zuul jobs ended up with broken Zuul config.
What's worse, it was failing only *some* jobs that were requiring these repos. As a result, for OpenStack-Ansible around 20 patches landed without gating, as docs job was the only passing one, it was sufficient to set Verified+2.
yeah, there is step#6[1] where we cleanup all references to avoid the error. I was expecting projects to do that in advance when retirement is proposed for example, I see Heat/puppet doing those before repo content and the project is being removed from infra. Anyway, I am going to continue that cleanup today most probably. Also, I agree to move step#6 before step#5 where we remove the project from infra. That will help to avoid such issues. I will propose the same in p-t-g. [1] https://docs.openstack.org/project-team-guide/repository.html#step-6-remove-... -gmann
сб, 11 мая 2024 г. в 03:49, Ghanshyam Mann gmann@ghanshyammann.com>:
---- On Wed, 24 Apr 2024 13:39:40 -0700 Ghanshyam Mann wrote ---
Hello everyone,
As you might know, the Sahara project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project.
I'm sending this email to propose the Sahara retirement and based on the response, I will proceed next.
Seeing no response to this email or no volunteer to maintain this project, I have proposed the retirement in governance:
- https://review.opendev.org/c/openstack/governance/+/919374
-gmann
[1] https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72
-gmann