From 684332235d091261e818d28ffe16ba3dd6e5cada Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Dec 13 2021 13:04:19 +0000 Subject: Say that change owners should subscribe to the fesco ticket https://pagure.io/fesco/issue/2646#comment-743791 --- diff --git a/modules/ROOT/pages/changes_policy.adoc b/modules/ROOT/pages/changes_policy.adoc index 6ed4e67..2240f6e 100644 --- a/modules/ROOT/pages/changes_policy.adoc +++ b/modules/ROOT/pages/changes_policy.adoc @@ -102,6 +102,7 @@ This includes Release Engineering, Fedora Packaging Committee, and trademark app The change owner may be asked to provide more details or address proposed concerns. FESCo members are encouraged to ask questions on the mailing list instead of waiting for the meeting. ** Optionally, FESCo assigns the change to one of the FESCo members or a trusted community member within the functional area (a _change shepherd_), who follows the detailed status of the change with FESCo and helps with processes within Fedora. For example, the change shepherd may communicate high-impact aspects of the change, or point out that a buildroot will be neccessary. The shepherd follows the status of the change until final release. +* Change owners are encouraged to subscribe to the FESCo ticket once it has been created by the Program Manager. * The Program Manager will create Bugzilla trackers in the _Changes Tracking_ component and issues in the Release Notes repository for approved changes. * FESCo will re-review the status of changes one week before the beta freeze. At this time, FESCo typically decides whether to activate the contingency plan.