From 0b73106d2ab7b9d051d843f802fca26fe19837db Mon Sep 17 00:00:00 2001 From: Stephen Gallagher Date: Apr 02 2019 17:42:48 +0000 Subject: Managing Defaults: Add explanation of modified field Indicate that if packagers send PRs for updating defaults, they must update the modified field. --- diff --git a/modules/ROOT/pages/making-modules/managing-defaults.adoc b/modules/ROOT/pages/making-modules/managing-defaults.adoc index 84e9bb1..bd392fc 100644 --- a/modules/ROOT/pages/making-modules/managing-defaults.adoc +++ b/modules/ROOT/pages/making-modules/managing-defaults.adoc @@ -11,7 +11,7 @@ Setting or changing a default stream or a default installation profile of a modu 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]. Please specify which releases of Fedora should have which streams/profiles by default in the initial ticket. -To check the current defaults, have a look at the https://pagure.io/releng/fedora-module-defaults[fedora module defaults repository]. +To check the current defaults, have a look at the https://pagure.io/releng/fedora-module-defaults[fedora module defaults repository]. If you submit a pull-request to change an existing default, this may be done only on the `master` branch and must be accompanied by updating the https://github.com/fedora-modularity/libmodulemd/blob/master/mod-defaults/spec.v1.yaml#L12[data.modified] value. 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.