#47 Modify the Change process SoP for script improvements
Merged 7 months ago by bcotton. Opened 7 months ago by adamwill.
fedora-pgm/ adamwill/pgm_docs changes-process-drop-warning  into  main

@@ -19,9 +19,7 @@ 

  . Create new bugs with the https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/changes[scripts]

  .. Run `make version=<NN> type=<SystemWide|SelfContained> build` to download and parse the wiki pages

  .. Run `make bz` to create tracking bugs in Bugzilla.

- (See warning below for failure cases)

  . Edit the created bug

- .. Set the assignee to the first person listed on the Change page

  .. Add yourself to the _cc_ field

  .. Set the bug to block the `F<NN>Changes` tracking bug

  .. Set the bug status to `ASSIGNED`
@@ -39,9 +37,9 @@ 

  . If the Change involves a new Spin, add it to the xref:releases::index.adoc[Releases docs].

  

  WARNING: Bugzilla requires an email address to exist in the system in order to add it to a bug.

- If an email address listed on a wiki page does not exist in Bugzilla, you will have to update the `feature-pages.csv` file with the correct address (or remove it and add it later.)

- If you are processing multiple newly-approved proposals at once, re-running the script after correcting the email address may lead to duplicate bugs.

- Remove Changes with successful bug creation from `feature-pages.csv` or finish the above steps for the successful bugs before starting over with the failed bugs.

+ If an email address listed on a wiki page does not exist in Bugzilla, that address will not be CCed on the bug.

+ If no address listed exists in Bugzilla, the bug will remain assigned to the Change Wrangler.

+ In that case you should try and find an address for a Change owner that does exist in Bugzilla and re-assign it, or ask the Change owner(s) to register in Bugzilla.

  

  TIP: If the Change involves creating a new Spin, send the owners the xref:releases::spins/creating.adoc[Creating a Spin docs].

  Otherwise, the coordination with Websites et al will probably be overlooked.

I've made the script used in this SoP more robust (I hope), so
this warning can now be reworded. The script no longer crashes
on email addresses that don't exist in Bugzilla, and it should
avoid creating duplicate tracker bugs even if run multiple times
without the source CSV file being updated. Also, it now assigns
the bug to a Change owner automatically, so long as any listed
email address exists in Bugzilla.

Signed-off-by: Adam Williamson awilliam@redhat.com

rebased onto 9fadb0d

7 months ago

Pull-Request has been merged by bcotton

7 months ago
Metadata