operations/docs
operations/docs
3
0
Fork 5
Code Issues 2 Pull requests Activity Actions
docs/modules/ROOT/pages/pgm_guide/sop/release-new.adoc
Adam Williamson 92f9ff5b78 Substantially revise the release process guide 
This contained quite a lot of outdated information and steps
that were duplicated with the SOPs. This revises it to focus
on a full release cycle workflow, mainly linking out to the
release step SOPs, with a few remaining notes that don't fit
anywhere else kept at the bottom.

Note this entirely drops the notification of release-blocking
deliverables for a release - it was only done for F31 and F32,
and nobody seems to be missing it.

This also removes some duplication between the No-Go SOP and
the Release Delay SOP and has a few other small updates and
cleanups.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-09-21 16:19:01 -07:00

2.3 KiB
Raw Permalink Blame History

This document outlines procedures for new releases. Note that schedules are often generated up to three years in advance, so they are covered separately.

Timing/trigger

On or about a year before the target release date.

If a Change proposal is submitted for the release, that’s a good time to start this process.

Procedures

  1. Create a tracking bug in Bugzilla

    1. Create a bug in the "Changes Tracking" component

    2. Set the summary to "Fedora Linux NN Change proposal tracker"

    3. Set the description to "This is a tracking bug for FNN Changes."

    4. Click "Submit Bug" so you can add additional information

    5. Add "Tracking" to the Keywords field

    6. Click "Show advanced fields" if they’re not already visible

    7. Click "Edit" on the Alias and set it to "FNNChanges"

    8. Click "Save Changes"

  2. Add docs to the Releases module

    1. Make an fNN directory

    2. Copy the contents from the previous release to this directory

    3. Update the :release-version: macro in each adoc file

    4. Add listings to nav.adoc under the "Upcoming Releases" header. Copy the previous release’s entries and update version numbers as appropriate.

  3. Update the schedule

    1. Create a schedule for the new release, following the ../schedule[Schedule SOP]

    2. Add the new release to the index.html page on the web view of the schedule.

  4. Update the wiki Change pages for the new release

    1. Create the Releases/NN/ChangeSet page on the wiki. Use the template below for guidance

Wiki template for ChangeSet page
{{autolang|base=yes}}

{{admon/warning|DO NOT EDIT this page manually as it's generated automatically and all changes will be overwritten! If you want to change anything, change the original Changes page and it will be picked up in the next refresh. If not, ping [[User:bcotton|bcotton]].}}

[https://bugzilla.redhat.com/show_bug.cgi?id=FNNChanges Bugzilla tracking]

[[Category:FNN]]

__TOC__

{{Anchor|accepted_system_wide}}
== Fedora Linux NN Accepted System-Wide Changes ==

{{Anchor|accepted_self_contained}}
== Fedora Linux NN Accepted Self-Contained Changes ==

  1. Add the new release to the Changes wiki page