A few notes on Prioritized bugs
This commit is contained in:
parent
ef1fce5216
commit
310327e438
1 changed files with 25 additions and 0 deletions
25
modules/pgm_guide/pages/prioritized_bugs.adoc
Normal file
25
modules/pgm_guide/pages/prioritized_bugs.adoc
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
= Prioritized Bugs
|
||||
|
||||
The https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process[Prioritized Bugs] process is designed to get attention for issues that are not blockers but are still high-impact or high-visibility.
|
||||
The criteria are intentionally subjective and we will drop bugs from the list if we can't convince developers to make progress.
|
||||
|
||||
CAUTION: Some development teams used the *Triaged* keyword, which can mess with your Bugzilla queries.
|
||||
It may be worth changing the process to use a dedicated keyword.
|
||||
|
||||
We run the meeting every two weeks.
|
||||
It is open to anyone, but in practice it's usually the FPgM and FPL who attend.
|
||||
Send the nominated and open accepted bugs a day in advance to the triage (and optionally test and devel) mailing list.
|
||||
|
||||
TIP: Invite the assignees of nominated and accepted bugs so they can provide input.
|
||||
|
||||
TIP: Remind the QA team and the devel mailing list that this process exists so that they can nominate bugs and participate in meetings.
|
||||
|
||||
TIP: Editing the wiki by hand (despite the fact that it claims to be automated) stinks.
|
||||
Perhaps you can fork the Blocker Bugs code and use that to generate the list.
|
||||
Or perhaps you can write script that generates a static page.
|
||||
|
||||
NOTE: The https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process[wiki page] refers to *PM Score* and *PgM Internal* fields.
|
||||
These are a lie.
|
||||
Don't bother with them.
|
||||
|
||||
TIP: If you keep the https://pagure.io/fedora-pgm/pgm_communication/blob/master/f/prioritized_bugs.txt[IRC script] in the `pgm_communication` repo up-to-date, it will make it easier to prepare an agenda and keep status from meeting-to-meeting.
|
||||
Loading…
Add table
Add a link
Reference in a new issue