openstack
/
governance
Code Issues Proposed changes

Merge "No community goals for a release cycle"

This commit is contained in:
Zuul 2021-03-08 21:58:31 +00:00 committed by Gerrit Code Review
parent 0dee271391 ff79a011d3
commit 18fa78b5ec
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
goals/index.rst
View File

@ -79,7 +79,7 @@ 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
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
cycle. It can be zero 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
@ -236,6 +236,10 @@ during the current (say N) cycle timeframe.
Community goals
===============
It's not required to define community goals for each release cycle. The TC can
decide to not set any actionable community-wide goal for a release cycle,
leaving the projects to focus on whatever is most important in their scope.
.. toctree::
:maxdepth: 3