operations/docs
operations/docs
4
2
Fork 11
Code Issues 3 Pull requests 1 Activity Actions

Add Bugzilla housekeeping procedures

Browse source
This commit is contained in:
Ben Cotton 2019-10-02 16:39:07 -04:00
commit 7d4e0cf1cd
2 changed files with 143 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
modules/pgm_guide/nav.adoc
View file

@ -1,6 +1,5 @@
* xref:changes.adoc[Changes]
* xref:release_process.adoc[Release process]
* xref:housekeeping.adoc[Housekeeping]
* xref:prioritized_bugs.adoc[Prioritized bugs]
* xref:elections.adoc[Elections]
* xref:schedule.adoc[Schedule management]

145
modules/pgm_guide/pages/release_process.adoc
View file

@ -1,9 +1,86 @@
= Release Process SOPs
This section covers program management procedures related to the process of getting a release out the door.
The table of contents below is organized by category.
The document beyond that is in chronological order.
* xref:_gono_go_meeting[Go/No-Go meeting]
* xref:_release_readiness_meeting[Release Readiness meeting]
* *Meetings*
** xref:_gono_go_meeting[Go/No-Go meeting]
** xref:_release_readiness_meeting[Release Readiness meeting]
* *Bugzilla housekeeping*
** xref:_rawhide_rebase_warning[Rawhide base warning]
** xref:_branch_day[Branch day]
** xref:_release_day[Release day]
** xref:_eol_closure_reminder[EOL closure reminder]
** xref:_eol_day[EOL day]
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.
== Rawhide Rebase Warning
* Send the message below to devel-announce@lists.fedoraproject.org 1–3 weeks before the branch point.
....
Greetings,
This e-mail is intended to inform you about the upcoming Bugzilla changes
happening on TKTK (Rawhide bug rebase) and what you need to do, if anything.
We will be automatically changing the version for most rawhide bugs to Fedora TKTK.
This will result in regular bugs reported against rawhide during the Fedora TKTK
development cycle being changed to version 'TKTK' instead of their current
assignment, ‘rawhide’. This is to align with the branching of Fedora TKTK from
rawhide and to more accurately tell where in the lineage of releases the bug was
last reported.
Note that this procedure does not apply to bugs that are open for the ‘Package
Review’ or 'kernel' components or bugs that have the ''FutureFeature'' or ''Tracking'' keywords
set. These will stay open as rawhide bugs indefinitely.
If you do not want your bugs changed to version ‘TKTK‘, add the ''FutureFeature''
keyword. If you need help changing a large amount of bugs manually, we’d be glad
to help.
The process was re-approved by FESCo https://pagure.io/fesco/issue/1096 .
....
== Branch Day
=== Update product description
Adjust wording of the https://bugzilla.redhat.com/editproducts.cgi?action=edit&product=Fedora[Fedora product] in Bugzilla to reflect the branch.
....
Bugs related to the components of the Fedora distribution. If you are reporting a bug
against a stable release or a branched pre-release version please select that
version number. The currently maintained released versions are: Fedora N-1, Fedora N.
The branched pre-released version is Fedora N+1. If you have a bug to report against
the daily development tree (rawhide) please choose 'rawhide' as the version.
For more information about filing a bug against Fedora packages, see
https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/
....
=== Create N+1 version
* Create N+1 in Bugzilla's https://bugzilla.redhat.com/editversions.cgi?product=Fedor[Fedora product versions].
=== Rawhide Rebase
All of the following condiditions must be met:
* version == rawhide
* component != "Package Review"
* component != "kernel"
* opened against rawhide before 2019-08-13 (Rawhide Branching date is 2019-08-13)
* keyword ''FutureFeature'' is '''not''' present
* keyword ''Tracking'' is '''not''' present
* the string ''RFE'' is '''not''' present in the summary
* status != CLOSED
* You can use this https://bugzilla.redhat.com/buglist.cgi?classification=Fedora&f1=component&f2=creation_ts&f3=component&f4=bug_status&keywords=FutureFeature%2C%20Tracking%2C%20&keywords_type=nowords&list_id=8447069&o1=notequals&o2=lessthan&o3=notequals&o4=notequals&product=Fedora&query_format=advanced&short_desc=RFE&short_desc_type=notregexp&v1=Package%20Review&v2=2019-08-13&v3=kernel&v4=CLOSED&version=rawhide[Bugzilla query] to select bugs that meet the criteria above.
Save the results as a CSV file and run the https://pagure.io/fedora-project-schedule/blob/master/f/scripts/closebugs/fedora_rebase.pl[`fedora_rebase.pl` script] against it. For example:
`fedora_rebase.pl 31 bugs-2019-08-13.csv`
WARNING: This script will take a while to run.
Execute it from a machine with stable power and networking.
== Go/No-Go meeting
Before each public release, FESCo, QA, and Release Engineering meet to determine if the release criteria are met for a particular release.
@ -149,3 +226,67 @@ If an area needs help, use the `#help` command to raise it and coordinate among
#topic Websites
#topic Open floor
....
== Release Day
=== Update product description
Adjust wording of the https://bugzilla.redhat.com/editproducts.cgi?action=edit&product=Fedora[Fedora product] in Bugzilla to reflect the branch.
....
Bugs related to the components of the Fedora distribution. If you are reporting a bug
against a stable release or a branched pre-release version please select that
version number. The currently maintained released versions are: Fedora N-2, Fedora N-1,
and Fedora N. If you have a bug to report against the daily development tree (rawhide)
please choose 'rawhide' as the version.
For more information about filing a bug against Fedora packages, see
https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/
....
=== Cleanup of tracking bugs
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.
== 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.
Select all bugs for Fedora version N-2 that are not closed and save the results as a CSV file.
Run the https://pagure.io/fedora-project-schedule/blob/master/f/scripts/closebugs/fedora_eol_warning.pl[`fedora_eol_warning.pl` script] against it.
For example, to warn that Fedora 29 will be EOL on 19 November 2019:
`fedora_eol_warning.pl 29 2019-11-19 bugs-2019-10-22.csv`
WARNING: This script will take a while to run.
Execute it from a machine with stable power and networking.
== EOL day
=== Bug closure
All open bugs are closed on the EOL date.
Select all bugs for Fedora version N-2 that are not closed and save the results as a CSV file.
Run the https://pagure.io/fedora-project-schedule/blob/master/f/scripts/closebugs/fedora_close_eol.pl[`fedora_close_eol.pl` script] against it.
For example, to close Fedora 29 bugs with an EOL date of 19 November 2019:
`fedora_close_eol.pl 29 2019-11-19 bugs-2019-10-22.csv`
WARNING: This script will take a while to run.
Execute it from a machine with stable power and networking.
=== Update product description
Adjust wording of the https://bugzilla.redhat.com/editproducts.cgi?action=edit&product=Fedora[Fedora product] in Bugzilla to reflect the EOL.
....
Bugs related to the components of the Fedora distribution. If you are reporting a bug
against a stable release or a branched pre-release version please select that
version number. The currently maintained released versions are: Fedora N-1, Fedora N.
If you have a bug to report against the daily development tree (rawhide) please choose
'rawhide' as the version.
For more information about filing a bug against Fedora packages, see
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].