openstack/governance
Code Issues Proposed changes

Make inactive projects timeline as release milestone-2 of the cycle

Browse Source 
In current timeline for the inactive projects is the final release
of the cycle which will be little late for the release team to
finish the release work if inactive project become active. Release
milestone-2 is better time to do the check if any inactive projects
needs to be moved to active or retired.

Change-Id: I6ff58fbef50d3fe10f6622330477ada127fcaf18
This commit is contained in:
Ghanshyam Mann
2022-12-08 16:58:54 -06:00
parent 93386e5197
commit 38fdf9261d
1 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
reference/emerging-technology-and-inactive-projects.rst
View File

@@ -75,18 +75,18 @@ timeframe, TC will discuss with the team if more time is required for the
project to meet the :doc:`new-projects-requirements` or will retire the project.
An existing project should be reinstated as an active OpenStack project before
the final release of the cycle they entered the ``inactive`` state to be become
``active`` again and to be released in that cycle. In the case where an
``inactive`` project does not become ``active`` before the end of the cycle,
there will be no release of it proposed by the release team in that cycle. In
such a case it is up to the project itself to get CI working and propose a
release if that is needed. It may be required like that for example when there
will be some security fixes or compatibility fixes merged in the project.
In the case where an ``inactive`` project still does not become ``active``
during the next cycle after the cycle they entered the ``inactive`` state, TC
will discuss with the team if project will be retired before final release
in the release cycle. In such a case there will be no new releases of that
project.
the release milestone-2 of the cycle they entered the ``inactive`` state to
become ``active`` again and to be released in that cycle. In the case where an
``inactive`` project does not become ``active`` before the release milestone-2,
there will be no release of it proposed by the release team in that cycle.
In such a case it is up to the project itself to get CI working and propose
a release if that is needed. It may be required like that for example
when there will be some security fixes or compatibility fixes merged in the
project. In the case where an ``inactive`` project still does not become
``active`` during the next cycle after the cycle they entered the ``inactive``
state, TC will discuss with the team if project will be retired before the
release milestone-2 of the cycle. In such a case there will be no new releases
of that project.
Tracking
========