English
[1] https://pagure.io/fedora-pgm/pgm_team/issues?status=Open&tags=spins+keepalive&close_status=
[2] https://fedoraproject.org/wiki/Releases/30/Spins
[3] https://pagure.io/fedora-pgm/pgm_team/new_issue
A couple of days before the deadline, send an email to spins and devel-announce mailing lists saying which ones will be retired. If no one adopts them, file a ticket with Release Engineering to stop producing the spin and with the Websties team to remove them from the website for the next release.
#action bcotton to announce decision
Add the EOL version and date to the https://fedoraproject.org/wiki/End_of_life[End of Life wiki page].
Add the new release to the https://fedoraproject.org/wiki/Changes[Changes wiki page].
Add the new release to the https://fedoraproject.org/wiki/Releases[Releases wiki page].
Add the **Tracking** keyword
Adjust wording of the https://bugzilla.redhat.com/editproducts.cgi?action=edit&product=Fedora[Fedora product] in Bugzilla to reflect the branch.
Adjust wording of the https://bugzilla.redhat.com/editproducts.cgi?action=edit&product=Fedora[Fedora product] in Bugzilla to reflect the EOL.
A few weeks before the deadline, create Pagure tickets for the spins and tag the appropriate owner. Then you can send this email to devel-announce and spins mailing lists (update the date and versions):
After the meeting is over, award participants the https://badges.fedoraproject.org/badge/readiness[Readiness badge].
#agreed Fedora 31 Beta is GO
#info Fedora 31 Beta will release on 2019-09-17
--- or ---
#agreed Fedora 31 Beta is NO-GO
#info The next F31 Beta Go/No-Go meeting will be Thursday, 2019-09-19 at 1700 UTC
All of the following condiditions must be met:
All open bugs are closed on the EOL date. Select all bugs for Fedora version N-2 that are not closed and save the results as a CSV file. Do this for both the **Fedora** product and the **Fedora Container Images** product. Exclude bugs with the **Tracking** keyword. This {bugzilla_eol_query}[Bugzilla query] will give you the right results (just update the version).
announce the result and the next meeting details to the devel-announce, test-announce, and logistics lists
announce the result to the devel-announce, test-announce, and logistics lists
A week before the branch point, create the release-blocking page in the wiki (see https://fedoraproject.org/wiki/Releases/31/ReleaseBlocking[the F31 page as an example]). Email this to the devel mailing list. Any edits should have been included in Change proposals, but it's a good opportunity to catch anything that got overlooked.
Before each public release all of the groups participating the development of Fedora's next release meet to make sure the release is well-coordinated. This meeting is called the https://fedoraproject.org/wiki/Release_Readiness_Meetings[Release Readiness Meeting]. The FPgM is responsible for scheduling and leading this meeting.
Before each public release, FESCo, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the https://fedoraproject.org/wiki/Go_No_Go_Meeting[Go/No-Go Meeting]. FPgM is responsibile for scheduling and leading this important meeting.
Branch Day