- Jerma Release Requirements
- Project Participation in the Jerma Release
- Jerma Release Schedule
- Project Release Planning Template
- Jerma Release Highlights
Release Process Description
The OPNFV release process consists of just two milestones followed by a series of release candidates. For each milestone and release candidate, individual project status is assessed by the TSC, based on completion of milestone tasks documented in Jira. In addition, the TSC will also assess the status of any OPNFV level requirements to determine whether the remain viable, or should be reduced in scope.
Milestone 1 (M1) - Planning
The M1 milestone is the point in the release process where project teams have completed their release planning documents, as well as any other release planning tasks associated with M1. In addition, all of the OPNFV-level requirements will be documented in the RELREQ project in JIRA and will be approved by the TSC.
OPNFV-level requirements are documented using RELREQ-1 - Getting issue details... STATUS .
- Clone RELREQ-1
- Make sure that the "fix version" field is set to Jerma
- Fill in the data under each heading in the Description field.
- Each project that will be working on the requirement should create a Story Jira issue in their project Jira, and attach it to the RELREQ Jira as a dependency.
- Complete a release plan, using the Project Release Planning Template
- Document all features, tasks, and bugs in Jira and set the "fix version" field to Jerma
Milestone 2 (M2) - Readiness Review
The readiness review milestone enables the TSC to assess the status of every project participating in the release, as well as the status of OPNFV-level requirements approved for the release.
- Resolve high priority Jira issues
- Complete preliminary documentation
- Document significant accomplishments
Preparation for Integration Testing (CNTT dependent projects)
Following M2, but well prior to RC0, projects that are a dependency of Common NFVI Telecom Taskforce (CNTT) work product must apply an RC tag to their repos and submit their code artifacts (e.g., container, compressed file) to the integration team for integration testing.
Some time after M2, but prior to RC0, the marketing team will present the release marketing message document to the TSC for review. The marketing message document will be based on input from the project teams about their significant accomplishments (see Project Tasks). The TSC will review the document and provide feedback to the marketing team.
Release Candidate (RCx)
Note that the RC milestones are intended primarily for projects that are dependencies of CNTT. However, all projects are encouraged to use these milestones to gauge their own progress.
There will typically be 2 or 3 release candidates, as determined by the TSC. The goal of the release candidate is to pass increasingly strenuous integration testing. The RC milestone is passed when the integration team indicates that the test criteria (TBD) for the RC has passed.
Prior to each RC milestone, projects will apply an RC tag to their code repos and provide code artifacts to the integration team for testing.
Final Release Candidate (RCn)
In addition to the requirements for RCs mentioned above, the following tasks will be performed.
- Resolve all issues assigned to the release
- Complete final documentation
The marketing team will present the message document, updated with TSC feedback, to the TSC.
Following the successful completion of the final release candidate, the TSC will vote on whether to approve the release.
- Apply release tag to repos
- Provide release artifacts to release engineering
The marketing release is handled by the marketing team. Activities may include a press release and updating the software downloads page on the OPNFV website, among other things.
- No labels