...
Info |
---|
|
- Use the "Copy" and "Move" options option (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
|
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|
Product Management |
All Have all JIRA Stories supporting the release use case been implemented? | Yes | Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project=vfc and type=Story and fixversion="Amsterdam Release" |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release" |
List the Stories that will not be implemented in this current Release. |
Provide link to JIRA Query listing the stories that will not be implemented in current stories. (Example for AAI project)No | Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project=vfc and type=Story and fixversion="Beijing Release" |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release" |
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes |
Provide Link to Project backlogVF-C Backlog |
|
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes |
Has all Product Backlog not implemented in current release been scoped for next release?Provide link to issue scoped for next release |
|
|
Release Management | Have all issues pertaining to FOSS been addressed? | Yes |
|
|
Have all findings from previous milestones been addressed? |
Provide link to JIRA findings | Yes
| List previous milestone issues that have not been addressed. | For M2 and M3 Milestones, ensure all findings have been closed. |
Development | Are all Defects of priority Highest and High in status "Done" in Jira? | Yes | Provide link to JIRA issue (type bug) of priority Highest and High. Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project=vfc and type=Bug and fixversion="Amsterdam Release" and Priority=High |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
|
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | No
| (note: emsdriver include vesjavalibrary jar file) | Refer to CI Development Best Practices |
Is there any pending commit request older than 36 hours in Gerrit? | No |
|
|
Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes |
Provide link to "Merge job" as evidence in Jenkins project tabProvide link to evidenceVF-C binaries in Nexus |
|
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes |
| Contact the upstream teams to make sure they will release their artifacts (in Nexus Release repo) so you can build by depending on these released artifacts by RC0. |
Integration and Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? |
In Progress each repositories?In ProgressAdd a link toward the your project documention in ReadTheDocs.AAF VF-C API List | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |