On Wed, Jun 12, 2019 at 04:39:07AM -0400, Jakub Cajka wrote:
> F31 change page:
>
https://fedoraproject.org/wiki/Changes/Adopt_new_Go_Packaging_Guidelines
> and approval:
https://pagure.io/fesco/issue/2120
It seems that this change has been accepted as Self Contained Change
but IMHO it is System Wide Change as it seems to affect (nearly) all
Go based packages in distribution(and will require work/attention of
people that are not change owners, actually not accounted for in
change proposal). For past several releases I have been doing rebase
of Go compiler change(yet to be filed for F31) that is IMHO
comparable(maybe a bit smaller) in scope and they were always deemed
by FESCO as System Wide Changes. This really leaves me
confused. Could someone from FESCO clarify?
https://fedoraproject.org/wiki/Changes/Policy#Self_contained_changes says
Examples include [...] a coordinated effort within a SIG with
limited impact outside the SIG's functional area
So in this case, even though the change affects so many packages, it
falls into the "self contained change" category.
That said, the difference between "system-wide" and "self-contained"
boils down to two things: some additional data required in the change
page, and filing the change a bit earlier. In this case the additional
data is mostly there in the change page, and the change was filed early,
so even if we were to change the Change to "system-wide", the effect
would be cosmetic.
Zbyszek