operations/docs
operations/docs
3
1
Fork 10
Code Issues 4 Pull requests 1 Activity Actions

Remove the Release Readiness Meeting

Browse source 
We haven't done it in a while and it's mostly gone unnoticed
This commit is contained in:
Ben Cotton 2021-11-30 15:14:52 -05:00
commit adacaf0b51
1 changed files with 0 additions and 58 deletions
Download patch file Download diff file Expand all files Collapse all files

58
modules/ROOT/pages/pgm_guide/release_process.adoc
View file

@ -270,64 +270,6 @@ QA?
For slippages of more than two or three weeks, you may need to propose a change to the subsequent schedules.
A final release slip likely does not require slipping the subsequent release unless it is longer than a month.
== Release Readiness meeting
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.
=== Occurrence
This meeting is held for every public release (Beta and Final), but only once for each milestone.
=== SOP
TIP: The current process is not great.
It requires teams to have a representative present at a particular time and if something is wrong, it may be too late to solve the problem before the release.
This meeting needs some re-evaluation in order to ensure it is useful to the community.
==== Pre-meeting
* Schedule the meeting in Fedocal's https://apps.fedoraproject.org/calendar/Fedora%20release/[Fedora release] calendar. The Go/No-Go meeting is traditionally held on the Thursday prior to the first scheduled release date from 19:00–21:00 UTC.
Select an available meeting channel.
#fedora-meeting-1 has generally been available at this slot.
It is best to set the meeting to recur weekly for 3 weeks in case of multiple slips.
* Send an email 5–7 calendar days before the meeting to as many mailing lists as you can think of plus https://discussion.fedoraproject.org[Discussion] in order to reach as many stakeholder groups as possible.
==== During the meeting
Go through each area and check for their status.
(You will probably get a lot of no-answers.)
Use the `#info` command to record statuses for the minutes.
If an area needs help, use the `#help` command to raise it and coordinate among attendees to resolve the issue or follow up on it.
After the meeting is over, award participants the https://badges.fedoraproject.org/badge/readiness[Readiness badge].
===== IRC script
....
#startmeeting F[version] [milestone = Beta, Final] Readiness Meeting
#meetingname f[version]-[milestone = beta, final]-readiness-meeting
#topic Roll Call
#chair [xxx]
#topic Purpose of this meeting
#info "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."
#link https://fedoraproject.org/wiki/Release_Readiness_Meetings
#topic Current status
#topic Ambassadors
#topic Design
#topic Documentation
#topic FESCo
#topic Fedora Engineering Manager
#topic Fedora Project Leader
#topic Marketing
#topic Infrastructure
#topic QA
#topic Release Engineering
#topic Translations
#topic Websites
#topic Open floor
....
== Release Day
=== Finalize ChangeSet page