From 3a4b80a2dbf4f72a439007befab93f4a6052baec Mon Sep 17 00:00:00 2001
From: Ben Cotton <bcotton@fedoraproject.org>
Date: Apr 13 2022 14:46:22 +0000
Subject: Add an SOP for new releases


This will need to get cleaned up with existing docs, but it's a start

---

diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 11542c5..9cb5d6e 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -25,5 +25,5 @@
 ** xref:pgm_guide/inactive_provenpackagers.adoc[Inactive provenpackagers]
 ** xref:pgm_guide/bugzilla_admin.adoc[Bugzilla admin]
 ** xref:pgm_guide/getting_started.adoc[Getting started]
-
-
+** SOPs
+*** xref:pgm_guide/sop/release-new.adoc[New releases]
diff --git a/modules/ROOT/pages/pgm_guide/sop/release-new.adoc b/modules/ROOT/pages/pgm_guide/sop/release-new.adoc
new file mode 100644
index 0000000..02c411c
--- /dev/null
+++ b/modules/ROOT/pages/pgm_guide/sop/release-new.adoc
@@ -0,0 +1,50 @@
+= New release SOP
+
+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
+
+. Create a tracking bug in Bugzilla
+.. https://bugzilla.redhat.com/enter_bug.cgi?component=Changes%20Tracking&product=Fedora&version=rawhide[Create a bug in the "Changes Tracking" component]
+.. Set the summary to "Fedora Linux NN Change proposal tracker"
+.. Set the description to "This is a tracking bug for FNN Changes."
+.. Click "Submit Bug" so you can add additional information
+.. Add "Tracking" to the Keywords field
+.. Click "Show advanced fields", if they're not already visible
+.. Click "Edit" on the Alias and set it to "FNNChanges"
+.. Click "Save Changes"
+. Add docs to the xref:releases::index.adoc[Releases] module
+.. Make an `fNN` directory
+.. Copy the contents from the previous release to this directory
+.. Update the `:release-version:` macro in each adoc file
+.. Add listings to `nav.adoc` under the "Upcoming Releases" header.
+Copy the previous release's entries and update version numbers as appropriate.
+. 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 ==
+....