On Fri, 2024-09-20 at 13:27 +0100, Erno Kuvaja wrote:
Hi all,
I'm aware that this might be unpopular opinion but I'll air it anyways.
Part of the problem seems to be, like Stephen well flagged, that it's very easy to miss the u-c bump failing. Perhaps it would make sense to take a step back on our release process and stop the bot submitting the bumps. Lets put that back as a manual task for the release liaison/PTL as part of the new release of the component.
i think that would make sense for openstack deliverable but for thrid party deps the bot should still do this.
That way the bump has a real life owner who is invested to monitor that it actually merges and the new release gets adopted. Automating all the boring things is very popular approach, especially when we have shrinking community. But as there is no-one responsible or invested in to look after the requirements, well we see the interest to participate on the requirements team size.
doing the uc bump is actully prety autroamted even without the bot you can just use the tox env to generate teh bump and just write your commit mesasge thats all the bot does anyway.
If we PTLs and release Liaisons would take active role to look after our requirements again, I do believe we would have healthier environment to work on and more eyes on the failures.
i dont think we actully even need ti to be the ptl or release liason though i agree they would make the most sense as teh default but i think any core team member should be able to propose the bump.
- Erno "jokke" Kuvaja