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

Add spins keepalive

Browse source
This commit is contained in:
Ben Cotton 2019-10-03 13:17:55 -04:00
commit 8de2d0ef58
1 changed files with 27 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

27
modules/pgm_guide/pages/release_process.adoc
View file

@ -19,6 +19,33 @@ The document beyond that is in chronological order.
TIP: You may choose to create a https://fedoraproject.org/wiki/Releases/31/HouseKeeping[wiki page] to track the status of housekeeping tasks, as has been done historically.
== Spins keepalive
In order to keep from shipping spins that no one is maintaining anymore, https://pagure.io/fesco/issue/1972[FESCo approved a process] where the Program Manager will check with spin owners to make sure they're still around and wanting to produce the spin.
The deadline corresponds with the Self-Contained Change deadline.
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):
....
FESco previously approved a requirement that Spin/Labs owners send a
keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[1] for all Spins and Labs listed on the wiki[2].
If you are the owner of one of those spins and labs, please reply in
the appropriate ticket by30 January 2019 to indicate the spin should
continue to be produced. If there is a spin or lab that does not have
an open ticket, please create one[3].
The reasoning for this is to not ship spins that are not actively
maintained. Future improvements to the release process that will allow
for teams to self-publish solutions will eventually remove the need
for these keepalives.
[1] https://pagure.io/fedora-project-schedule/issues
[2] https://fedoraproject.org/wiki/Releases/30/Spins
[3] https://pagure.io/fedora-project-schedule/new_issue
....
== Rawhide Rebase Warning
* Send the message below to devel-announce@lists.fedoraproject.org 1–3 weeks before the branch point.
....