| |
@@ -15,6 +15,7 @@
|
| |
[source,subs="attributes+"]
|
| |
....
|
| |
$ bodhi releases edit --name F{branched} --state current
|
| |
+ $ bodhi releases edit --name F{branched}F --state current
|
| |
....
|
| |
|
| |
Set the bodhi stable tag to point to updates instead of base repo
|
| |
@@ -103,8 +104,9 @@
|
| |
|
| |
== Check and set EOL on previous releases to reflect reality
|
| |
|
| |
- Check Bodhi for active releases and set respective EOL date. It's important to have an EOL date set,
|
| |
- because it serves for other scripts to distinguish between stable and branched releases.
|
| |
+ . check the fedora schedule for active releases and respective EOL date
|
| |
+ . if needed run the adjust-eol-all.py script from releng repository to
|
| |
+ correct any mistakes
|
| |
|
| |
== Make sure there are no tagging leftovers from bodhi
|
| |
|
| |
@@ -117,6 +119,10 @@
|
| |
the web server due to permissions. Typically we ask somebody from the
|
| |
Infrastructure team to give the tree a second set of eyes.
|
| |
|
| |
+ Some things to check for:
|
| |
+ . are the CHECKSUM files signed?
|
| |
+ . are the spins/labs present?
|
| |
+
|
| |
== Post Release
|
| |
|
| |
=== One Week After the Release
|
| |
Signed-off-by: Kevin Fenzi kevin@scrye.com