Add content about updating wiki and web pages

This commit is contained in:
Ben Cotton 2019-12-04 14:49:07 -05:00
commit 3a353d2224

View file

@ -16,9 +16,37 @@ The document beyond that is in chronological order.
* *Deliverables*
** xref:_release_blocking_deliverables[Release blocking deliverables]
** xref:_spins_keepalive[Spins keepalive]
* *Content*
** xref:_wiki_and_website_creation[Wiki and website creation]
** xref:_wiki_and_website_edits[Release day wiki and website edits]
** xref:_wiki_and_website_edits_2[EOL day wiki and webiste edits]
TIP: You may choose to create a https://fedoraproject.org/wiki/Releases/31/HouseKeeping[wiki page] to track the status of housekeeping tasks, as has been done historically.
== Wiki and website creation
There are so many places in the wiki to create things.
This is probably not an exhaustive list.
Hopefully in the future we'll have improved this process by consolidating and automating.
* Update the index.html page on the https://fedorapeople.org/groups/schedule/[web view] of the schedule.
* Create a release page (`Releases/N`) in the wiki that collects the pages in that category.
You can use `{{Special:PrefixIndex/Releases/N/}}` to make it automagic (replacing "N" with the release number).
This is a good target for de-wikifying.
* Create a release schedule page (`Releases/N/Schedule`) in the wiki.
For Fedora 31 and previous, this included a manually-transcribed copy of key milestones.
For Fedora 32 and beyond, Ben decided that's a good way to introduce human error and made that page point to the https://fedorapeople.org/groups/schedule/[web view] of the schedule instead.
* Create a ChangeSet page (`Releases/N/ChangeSet`) in the wiki.
The output of the link:../changes#_create_tracking_bug[change processing scripts] gives you the content for this page.
* Create a Spins page (`Releases/N/Spins`) in the wiki.
Copy this from the previous version and make any changes as appropriate.
This is another good target for de-wikifying.
* Create a Release blocking deliverables page (`Releases/N/ReleaseBlocking`) in the wiki.
Again, copy this from the previous version and make changes as appropriate.
Stop me if you've heard this before, but this is a good target for de-wikifying.
* Add the new release to the https://fedoraproject.org/wiki/Releases[Releases wiki page].
* Add the new release to the https://fedoraproject.org/wiki/Changes[Changes wiki page].
== Spins keepalive
In order to keep from shipping spins that no one is maintaining anymore, https://pagure.io/fesco/issue/1972[FESCo approved a process] where the Program Manager will check with spin owners to make sure they're still around and wanting to produce the spin.
The deadline corresponds with the Self-Contained Change deadline.
@ -291,6 +319,12 @@ https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/
Review all the tracking bugs for Changes and close those which are already implemented and delivered.
Tracking bugs of delivered Changes to be closed as `CURRENTRELEASE` resolution.
=== Wiki and website edits
* Update the index.html page on the https://fedorapeople.org/groups/schedule/[web view] of the schedule.
* Update the https://fedoraproject.org/wiki/Releases[Releases wiki page].
* Update the https://fedoraproject.org/wiki/Changes[Changes wiki page].
== EOL Closure reminder
The EOL closure reminder is posted to all bugs for Fedora N-2 a day or two after the GA date of a new release.
@ -342,3 +376,9 @@ https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/
=== Disable EOL version
* Disable the EOL release in Bugzilla's https://bugzilla.redhat.com/editversions.cgi?product=Fedora[Fedora product versions].
=== Wiki and website edits
* Update the index.html page on the https://fedorapeople.org/groups/schedule/[web view] of the schedule.
* Update the https://fedoraproject.org/wiki/Releases[Releases wiki page].
* Update the https://fedoraproject.org/wiki/Changes[Changes wiki page].