I think there would be a different expectation for "mature" projects.
It is quite difficult to define "fully functional" and "stable" since the projects never stop evolution even after mature. >From a developer's view, a mature project can be judged from 1. regular release cycle 2. test coverage 3. documentation completeness 4. security integrity 5. timely response on feedback 6. fluent process on evolution My two cents. On Thu, Nov 3, 2016 at 1:25 PM Raymond Paik <[email protected]> wrote: > All, > > One of my action items from the TSC meeting.... We discussed graduation > reviews for "mature" projects in OPNFV. On the Project Lifecycle document ( > https://www.opnfv.org/developers/technical-project-governance/project-lifecycle), > a mature project is defined as "Project is fully functioning and stable, > has achieved successful releases." > > One of the questions that was raised on the call was, after graduation how > would "mature" projects be different from projects in the "incubation" > stage. Is this just a badge/label or are there different expectations? > > Please discuss :-) > > Thanks, > > Ray > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
