Project lifecycle¶

List of states¶

The state names are short negative phrases describing what is missing to progress to the following state.

• non-existent The project is not recognized by Technical Steering Committee (TSC) to be part of OpenDaylight (ODL).
• non-participating The project is recognized byt TSC to be an ODL project, but the project has not confirmed participation in SR for given release cycle.
• non-building The recognized project is willing to participate, but its current codebase is not passing its own merge job, or the project artifacts are otherwise unavailable in Nexus.
• not-in-autorelease Project merge job passes, but the project is not added to autorelease (git submodule, maven module, validate-autorelease job passes).
• repo-not-in-integration Project is added do autorelease, but integration/distribution:features-index is not listing all its public feature repositories.
• distribution-check-not-passing Project is in autorelease, but its distribution-check job is either not running, or it is failing for any reason.
• feature-not-in-integration Feature repositories are referenced, distribution-check job is passing, but some user-facing features are absent from integration/distribution:features-test
• feature-is-experimental All user-facing features are in features-test, but at least one of the corresponding functional CSIT jobs does not meet integration/test requirements.
• ready