Most of the time, even after trying our best, we tend to miss out on some items for mass branching; either it is to check if rawhide definitions are correct, or if we made changes to all the files that need to get updated, etc; For the same, The SOP we have for mass_branching doesn't have a checklist yet - to track all the changes. This issue will grant us a way to collaborate and discuss a "logical" checklist for future releases.
For now: @jnsamyak will start fetching a document for this, and will share it with folks to discuss in releng weekly meetings.
When do you need this? (YYYY/MM/DD) Before the next mass branching
When is this no longer needed or useful? (YYYY/MM/DD) It will always be useful ;)
If we cannot complete your request, what is the impact? Long nights of figuring what we missed each time we branch :P
Just for reference, on the things that we missed while branching this time (f39) are listed here: https://hackmd.io/@jednorozec/HkIy8Ebh2/edit
In the checklist we need to add two things:
The initial draft for checklist is added here: https://pagure.io/infra-docs-fpo/pull-request/250
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.