The Modularity WG is changing the policy regarding module default stream changes & Fedora Changes. It is a minor policy change that doesn't require any changes in code. I'd like to get a formal +1 from FESCo on the change before publishing it.
The summary would be: "Instead of rigidly requiring a Fedora Change for all module default stream changes, we are relaxing the policy to 'submitting a Fedora Change based on packager's best judgement'. We are also restricting changes to major Fedora releases. This makes it more consistent with how we handle major changes in traditional packages."
For more details, please see the current policy [1] (please note it's described quite "efficiently"), the new policy approved by the Modularity WG [2], and optionally a set of scenarios covering module default stream changes [3].
[1] https://docs.fedoraproject.org/en-US/modularity/making-modules/managing-defaults/#_setting_or_changing_a_default [2] https://tree.taiga.io/project/modularity-wg/us/77 [3] https://pagure.io/modularity/working-documents/blob/master/f/lifecycles-upgrades-ownership/defaults-and-fedora-changes.md
+1
tl;dr:
+1 - the change proposal process isn't particularly scalable, and better to allow judgement in when one is required.
It seems to me that stream default changes should probably always be mentioned in release notes, so maybe require at least these all the time?
+1 from me as well.
It's been over a week and has +8. I'll announce this as approved.
Metadata Update from @sgallagh: - Issue tagged with: pending announcement
Announced
Metadata Update from @sgallagh: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Cool, thanks!
Metadata Update from @churchyard: - Issue untagged with: pending announcement
Login to comment on this ticket.