...

In these cases, a small team of TSC members will review the request, discuss it with stakeholders, and make a recommendation to the TSC whether to approve the request.  The intent is for the analysis and the decision to be made by the TSC, rather than by an individual.

Process

1. A project is notified that they have not fulfilled , Use Case, or Requirement is identified as NOGO for a release milestone requirement and that they are being dropped from the release. --OR-- A use case or requirement owner has been informed that their requirement will not be included in a release, based on code impact analysis.
2. If the the project PTL, or the requirement owner, dispute the assessment, then they may submit an exception request via the ONAP wiki.  Please complete all fields in as much detail as possible.
3. Once the form has been completed and saved, notify the release manager and the TSC chair that an exception request has been submitted.
4. The release manager will inform the review team, who will begin the review as soon as possible.
5. Once the review team has completed their assessment and developed a recommendation, they will inform the release manager and the TSC chair of their decision.
6. The TSC chair or the release manager will send mail to the TSC mailing list, informing the TSC of the decision.
7. A discussion and vote will be scheduled for the next TSC meeting.

Exception Request Review Team

• Team is composed of at least 5 community volunteers.
• The review team serves for two releases.
• There should be no more than one team member from any one company.
• Team members should recuse themselves if they have direct involvement with the project or requirement in question.