From cae6a24abfd8c1335b7168b6e85220c8a1fed507 Mon Sep 17 00:00:00 2001 From: Thierry Carrez Date: Thu, 22 Aug 2019 10:45:31 +0200 Subject: [PATCH] Subsequent fixes in goal selection process changes A number of small improvements were suggested during the review of the separation of goal definition from goal selection. Rather than update in place and lose the already-cast votes, let's propose those as a subsequent change. Change-Id: I76bda8256a8fad9a2aeea4208b6ff54f9ba9d7b9 --- goals/index.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/goals/index.rst b/goals/index.rst index c3f9250e8..0c25d00d0 100644 --- a/goals/index.rst +++ b/goals/index.rst @@ -78,14 +78,16 @@ planning and other discussion at the PTG event at the start of the cycle. To define goals for a release cycle, a TC member should first set up the new series-specific directory under ``/goals/selected/`` in one patch (for -example, create a ``/goals/selected/unicorn`` subdirectory for the Unicorn +example, create a ``/goals/selected/train/`` subdirectory for the Train release). Then a selection of goals can be proposed: a single subsequent patch moving a set of goals from the ``/goals/proposed/`` directory to the -new ``/goals/selected/$series/`` subdirectory. +new ``/goals/selected//`` subdirectory. This allows to consider the proposed series goals as a group, and take into account how feasible they are together, considering the timing and -cycle length. +cycle length. Champions for selected goals should +1 this patch to confirm +they are ready to work on their goal in the chosen cycle. + Tracking Goal Progress ----------------------