From 16c440e4113ffcd614b5d1a6ed21c7cd32f86d9b Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jan 23 2019 10:59:55 +0000 Subject: Update 'managing defaults and fedora changes' --- diff --git a/modules/ROOT/pages/making-modules/managing-defaults.adoc b/modules/ROOT/pages/making-modules/managing-defaults.adoc index 2a7d876..dedeb77 100644 --- a/modules/ROOT/pages/making-modules/managing-defaults.adoc +++ b/modules/ROOT/pages/making-modules/managing-defaults.adoc @@ -1,14 +1,17 @@ = Managing module defaults in Fedora -Setting or changing a *default stream* or a *default installation profile* of a module is in most cases similar to changing a major version of a package. Setting or changing the default stream or the default installation profile requires a Fedora Change request, and it is only allowed in between Fedora releases. +Setting or changing a *default stream* or a *default installation profile* of a module is in most cases similar to changing a major version of a package. The following rules apply: + +1. Module stream defaults should be only changed in anupcoming Fedora release +2. Changes of stream defaults should be communicated by a Fedora Change based on the change's significance and its maintainer's best judgement. +3. No default stream changes mid-release are permitted. +4. Introducing a new default stream not replacing any existing default stream or a traditional package is not considered a change. That means it can be done. == Setting or changing a default -Submit an issue to Fedora Release Engineering in https://pagure.io/releng/issues[pagure.io/releng]. You also need to https://fedoraproject.org/wiki/Changes/Policy#For_developers[submit a Fedora Change]. +Submit an issue to Fedora Release Engineering in https://pagure.io/releng/issues[pagure.io/releng]. Consider https://fedoraproject.org/wiki/Changes/Policy#For_developers[submiting a Fedora Change]. To check the current defaults, have a look at the https://pagure.io/releng/fedora-module-defaults[fedora module defaults repository]. -Setting or changing default stream of a module will be considered based on the following rules: +Please note that if the module stream masks part of the Traditional RPM repos (e.g it replaces an existing RPM or it introduces a non-trivial set of conflicts) it may not be made a default stream without the express permission of FESCo. Release Engineering will be responsible for escalating any PR that is questionable on this point to FESCo for a final decision. -* If the module stream does not mask any part of the Traditional RPM repos, it may be set as a default stream. For example, any module that is entirely a leaf or one that fulfills the function of a package moved from the traditional repos into the modular repos (e.g. `nodejs:8` might replace the `nodejs` traditional package) -* If the module stream masks part of the Traditional RPM repos (e.g it replaces an existing RPM or it introduces a non-trivial set of conflicts) it may not be made a default stream without the express permission of FESCo. Release Engineering will be responsible for escalating any PR that is questionable on this point to FESCo for a final decision.