The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? |
By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example| Yes | | Jira |
|---|
| server | ONAP JIRA |
|---|
| jqlQuery | project = |
|---|
|
|
aai typeStory fixversion="Amsterdam Release" | issuetype != Bug | | count | true |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
|
|
for AAI project, edit for your project) | 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. |
By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example| Yes | | Jira |
|---|
| server | ONAP JIRA |
|---|
| jqlQuery | project= |
|---|
|
|
aai and fixversion| and status != done and status != " |
|
|
Beijing Release| in progress" | | count | true |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
|
|
for AAI project, edit for your project) | 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? |
Provide Link to Project backlog| No | Chasing this ... |
|
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | - |
|
|
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes |
|
|
| Have all findings from previous milestones been addressed? |
List previous milestone issues that have not been addressed| Yes | AFAIK. | 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? |
Provide link to JIRA issue (type bug) of priority Highest and High. | No | | Jira |
|---|
| server | ONAP JIRA |
|---|
| jqlQuery | project=log and type=Story and priority in (high, highest) and status != done |
|---|
| count | true |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
|
|
|
| Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | No |
| Refer to CI Development Best Practices |
| Is there any pending commit request older than 36 hours in Gerrit? | No | Gerrit |
|
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? |
Provide link to "Merge job" as evidence in Jenkins project tab| - | Cross-cutting. Commits are to OOM and other ONAP projects. |
|
| Are all snapshot binaries available in Nexus? |
Provide link to evidence | - | Cross-cutting. Commits are to OOM and other ONAP projects. |
|
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | - |
| 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? | N/A | All jobs pertaining to your project MUST pass |
|
| Is there a Docker images available for your project deliverable? | N/A | Provide link to Nexus repos |
|
| Has the project code successfully passed the Daily Build process? | Yes | Cross-cutting. Commits are to OOM and other ONAP projects. | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
| Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? |
Add a link to your project documentation in ReadTheDocs| Yes | Due September 25th, but hasn't appeared yet. | Documentation Team is using Readthedocs for documenting user facing documentation. ReadTheDcos shall be considered as a starting point for someone new within ONAP. The ReadTheDocs is the ONAP Documentation facade visible to users. Link to Templates How to setup the template for my project? |
| Is the API documentation section populated? |
Link to evidence | No | See above. It's pending, but we have all the content! Here: ONAP Application Logging Guidelines v1.1 | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |
