Merge "Update goal selection docs to clarify the goal count"
This commit is contained in:
@@ -78,6 +78,13 @@ Selecting goals for a cycle
|
|||||||
The TC will consider proposed goals from the ``/goals/proposed/`` directory
|
The TC will consider proposed goals from the ``/goals/proposed/`` directory
|
||||||
and select a set of OpenStack-wide goals for each cycle in time to allow
|
and select a set of OpenStack-wide goals for each cycle in time to allow
|
||||||
planning and other discussion at the PTG event at the start of the cycle.
|
planning and other discussion at the PTG event at the start of the cycle.
|
||||||
|
There is no minimum or maximum limit on the number of goals to be selected per
|
||||||
|
cycle. It can be one or more depends on the complexity and work required per
|
||||||
|
goal. Also, it is completely fine to skip goal for any cycle with a valid reason
|
||||||
|
for example, if any previous cycle goal is still pending and need more time to
|
||||||
|
complete, or project team has less bandwidth and working on other priority
|
||||||
|
items like popup team work etc.
|
||||||
|
|
||||||
|
|
||||||
To define goals for a release cycle, a TC member should first set up the
|
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
|
new series-specific directory under ``/goals/selected/`` in one patch (for
|
||||||
|
|||||||
Reference in New Issue
Block a user