Hello Folks,
I am initiating this ticket to facilitate the organization and documentation of cleanup tasks following our upcoming release. The objective is to develop a comprehensive checklist that will be integrated into our Standard Operating Procedures (SOPs) for future reference.
Initially, I will enumerate all items and branches that I anticipate will require attention post-release. However, I encourage each of you to contribute by identifying additional elements that may need to be addressed. Please add these to the ticket so we can ensure a thorough cleanup and maintain a cohesive record for subsequent use.
Thank you!
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Metadata Update from @jnsamyak: - Issue tagged with: docs, high-gain, medium-trouble, ops
Looking at this, I have two items for the post-clean-up section:
If there is anything else, please add it here. Once we have this finalized we could add it to the docs; starting here pr 1 of many: https://pagure.io/infra-docs-fpo/pull-request/289
CC: @kevin @humaton
We typically wait and do 2 a week or so out... this is because at release time, many more mirrors have development/40 than releases/40. The extra week gives time for all the mirror network to sync up and have things in the right place.
Here's my list:
week or so after release:
Remove /pub/alt/stage/* Beta and Final RC's. I usually check with QE to make sure they are not needing them for anything anymore before doing so. || NOT DONE
Remove all but the last/latest compose under /mnt/koji/compose/branched/ and /mnt/koji/compose/40/ || NOT DONE
two weeks after release after above is done:
Another one:
Thanks @kevin for bringing these up, I'll add these to sip and start closing them: When you say close all open issues, do you mean all of these: https://pagure.io/releng/failed-composes/issues or just related to f40 (the current branched)?
Great! Please let me know if you hit any problems with anything... I did already clean up the composes/40/ ones...
Yea, I meant all of them... if there was some old rawhide one we wanted to look at we could find it in closed. It might be nice to figure a way to disable notifications when doing that... so people don't get thousands of emails/fedmsgs... but if not I'm sure we can deal. :)
Docs are ready for the review: https://pagure.io/infra-docs-fpo/pull-request/292
Once I get a +1 on the PR I'll merge it and close this issue
Thanks @kevin for the doc review, I am closing this issue now!
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.