|Spins keepalive SOP|
|This document outlines procedures for the Spins keepalive process. This process was https://pagure.io/fesco/issue/1972[approved by the Fedora Engineering Steering Committee] to ensure that xref:releases::spins.adoc[Spins and Labs] are actively maintained.|
|The process begins two weeks before the Self-Contained Change proposal deadline.|
|The first step is to create keepalive tickets for each Spin/Lab. Create these in the https://pagure.io/fedora-pgm/schedule/[schedule repo].|
|Click the *New issue* button|
|Set `<Spin/Lab name> keepalive` as the issue title|
|Use `<@maintainer ID(s)> FESCo [approved a requirement](https://pagure.io/fesco/issue/1972) that Spin/Labs owners send keepalive request in order to keep building the spin or lab. Please confirm that you want the <Spin/Lab name> to continue for Fedora Linux <release>` as the comment.|
|Apply the *spins keepalive* tag.|
|Click *Create Issue*|
|Ignore the Test Days spin. It's useful to QA, but we don't release it publicly.|
|Next, send an email to the https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/[devel-announce] and https://lists.fedoraproject.org/archives/list/spins%40lists.fedoraproject.org/[spins] mailing lists (update the date and release):|
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 for all Spins and Labs for this release.
If you are the owner of one of those spins and labs, please reply in
the appropriate ticket by <DATE>> 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.
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.
|You may choose to nudge maintainers after a week.|