...
- Release, Security and Documentation scopes are now tracked via JIRA
- Adoption to “Do not break the build” principle
- No Vendor equipment is required for this release
- No new VNF requirement identified by the project team
- Jenkins Jobs Failures are monitored and fixed by the project team
- Health check and regression tests issues are reported by the Integration Team
- Project Team defines their Sprint content based on TSC prioritization to meet the delivery deadlines
- Inform TSC about any descope content post-M1 before changing FixVersion
JIRA Template
Note that these Epics and Tasks are cloned into the JIRA project for each individual ONAP project.
Jira server ONAP JIRA columns key,summary,type,created,updated,due,priority,status,resolution,epic name maximumIssues 20 jqlQuery project = CIMAN AND labels = relman AND issuetype = Epic ORDER BY updated DESC serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
- All high/highest priority jira tickets addressed
- Remaining License scan, security critical issues addressed
- Update Release note and documentation
- Docker images “Release” dues
- Project specific test plan for El Alto completed
- Update Risk Register
- Integration Weather Board complete
- Review of release notes and documentation
- Versioning at the project level
- Check the certification expiry of your application. It should be valid for the next 9 months after RC0.
Sign-off
- Remaining high/highest priority jira tickets addressed or workaround documented
- Close/move all open/in-process jiras to a future release
- Integration "Sign-Off" on Docker images “Release”
- Release notes and documentation completed
- OOM tag release and version in helm chartUpdate Manifest