fedora-pgm / pgm_docs

#49 Improvements to Change process documentation
Merged by bcotton. Opened by adamwill.
fedora-pgm/ adamwill/pgm_docs change-lifecycle-improvements  into  main

Download 49.patch

This updates the Change announcement SOP to be in-line with
the current practice followed by @amoloney (in the absence of
clearer guidance from FESCo for the Discourse changes, so far).
It adds a new SOP for dropping Changes (which is different from
deferring them), and extends the PgM Guide Changes page and the
top-level Changes SOP page to link to all the individual SOPs
(a couple were missing in each case) and also explain how a
Change's lifecycle is ultimately completed (in the Release Day
SOP).

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

This addresses https://pagure.io/fedora-pgm/pgm_docs/issue/46 , at least as best we can right now.

rebased onto e0eae0b42ca0b12cbd7ec7ffea9a7ee644b6a0aa

I disagree with clearing the targeted release field, but not enough to block this. Creating a Change_Drooped_Banner similar to the Change_Rejected_Banner is probably good idea for Future Totally-Not-Ben

Pull-Request has been merged by bcotton

what would you set the target release field to, for a dropped change? I couldn't think of an answer to that, so I went with clearing it.

Also, I am all about the drooped changes. :D

I'd leave it. It was targeted for that release, but it wasn't landed. NBD though

Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.