Spins keepalive SOP

This document outlines procedures for the Spins keepalive process. This process was approved by the Fedora Engineering Steering Committee to ensure that Spins and Labs are actively maintained.

Timing/trigger

The process begins two weeks before the Self-Contained Change proposal deadline.

Process

  1. Click the New issue button in the schedule repo.

  2. Select '<spins_labs_keepalive>' as the issue template

  3. Set <Spin/Lab name> keepalive as the issue title

  4. Update the body of the ticket with the maintainer name, deadline date and Fedora Release #

  5. Apply the spins keepalive tag, target release as the milestone and assign the ticket to the maintainer

  6. Click Create Issue

  7. Once all spins and labs keepalive requests are filed, send an email to the devel-announce and spins mailing lists (update the date and release):

  8. After one week, send a reminder email

  9. At the deadline, send a final email

  10. After one week post the deadline, send a notification email that the spin or lab will be dropped for this release and follow removal process.

  11. File the respective tickets for dropped spins/labs (see removal process below)

Ignore the Test Days spin. It’s useful to QA, but we don’t release it publicly.

Notfication of Keepalive Requests

To notify maintainers that the keepalive deadline is coming up, the first step is to create keepalive tickets for each Spin/Lab as listed above. The ticket is templated so you need to just update the fields and tag the ticket correctly. The email template to then send announcing the spins and labs keepalive requests is as follows:

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 for this release[2].

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[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-pgm/schedule/issues?status=Open&tags=spins+keepalive
[2] https://docs.fedoraproject.org/en-US/releases/f<RELEASE>/spins/
[3] https://pagure.io/fedora-pgm/schedule/new_issue

Deadline

At the deadline, send this email to the devel-announce and spins mailing lists with a list of spins that have not been kept alive.

The following Spins/Labs maintainers have not indicated they wish to
continue producing the deliverables for the upcoming release. Any
that have not been adopted in one week will be dropped.

* <list of Spins/Labs>

Process for Removal

One week after deadline, if=f there are still Spins/Labs that have not been adopted or had the current maintainer send a keepalive,

  1. Open a Release Engineering issue to have those deliverables removed.

  2. Open a Websites issue to remove the deliverables from the website for the release.

Submit the removal ticket before branch day so that the images are never produced for that release.
Spins and Labs maintainers who engage in the keepalive ticket should file their own removal request or change of ownership PR, but it is always good practice to confirm with them that these steps are completed in the ticekt.

Want to help? Learn how to contribute to Fedora Docs ›