OPNFV will use an exception process to manage projects that do not meet key release milestones. The release manager will determine which milestones are subject to the exception process. For example:
- MS2: Test case documentation (i.e. test case database)
- MS3: Installer / OpenStack integration
- MS5: Scenario integration and feature freeze
- MS6: Test case implementation
- MS10: Documentation completed
- If a project is unable to meet the requirements of a milestone by the scheduled date, then they will have a 1-week grace period to recover.
- If the requirement still has not been met by the end of the grace period, then, at the release manager's discretion, the project must either withdraw from the release, or request a milestone exception by completing the exception request form, then notifying the release manager by email, who will schedule the review.
- The exception request will be reviewed by a volunteer team, who will make sure that the exception is clear and comprehensive.
- The exception request will be evaluated for its impact on the entire schedule, including the likelihood of missing other milestones. The intent is to capture the entire impact and avoid having an exception request for every milestone missed.
- The exception will be presented to the TSC, who will discuss and vote on the request.
- If the exception is approved:
- The milestone date will be rescheduled for the project, OR
- The milestone will be exempted, entirely
- If the exception is accepted, but the plan for recovery fails, then the project must withdraw from the release.
- If the exception is denied, then the project must withdraw from the release.
This criteria will be used to evaluate exception requests prior to being submitted to the TSC for approval (see step #2 under "Process" above).
- The exception request is complete.
- The recovery plan is realistic,
- The recovery plan includes detailed steps with a schedule so that the progress can be monitored.