openstack
/
governance
Code Issues Proposed changes

Add a requirement for deprecating duplicated code 

This patch updates graduation requirements related to scope.  The requirements
currently say a project must not duplicate the scope of another project.
However, we have some cases where a project intentionally duplicates
functionality with the intent of replacing it (Neutron, Cinder).

In that case, I believe we should have an additional requirement that the new
project may not graduate until it has reached a level of functionality and
maturity where we're able to deprecate the component it is replacing with a
known timeline for removal.

Change-Id: I5305e2f80ebc3c78ef74b0957337fe11c3f3de08
This commit is contained in:
Russell Bryant 2014-01-31 13:15:56 -05:00
parent 5b7e5ee34d
commit 36b5149b53
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
reference/incubation-integration-requirements
View File

@ -62,7 +62,12 @@ evaluate the technical maturity of the project and check a number of
requirements, including (but not limited to):
* Scope
** Project must not duplicate functionality present in other OpenStack projects
** Project must not duplicate functionality present in other OpenStack projects,
unless the project has intentionally done so with the intent of replacing it.
** In the case that a project has intentionally duplicated functionality of
another project, or portion of a project, the new project must reach a level
of functionality and maturity such that we are ready to deprecate the old
code and remove it after a well defined deprecation cycle.
* Maturity
** Project must have a large and diverse team of contributors