• Describe the issue

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 RelEng and 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

• When do you need this? (YYYY/MM/DD)

No date.

• When is this no longer needed or useful? (YYYY/MM/DD)

No date.

• If we cannot complete your request, what is the impact?

Packagers would continue to be required to submit a Fedora change for every module default stream change, even in cases one wouldn't be submitted in a similar change introduced by traditional packages — making the workflows between the two delivery methods (trad packages & modules) inconsistent.