Skip to end of metadata
Go to start of metadata

DRAFT PROPOSAL FOR COMMENTS

This checklist is expected to be completed for the project to pass the M1 Release Planning Milestone.

M1 Release Planning Milestone definition

Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)


Practice AreaCheckpointYes/NoEvidence - CommentHow to?
SecurityHas the Release Security/Vulnerability table been filled out in the protected Security Vulnerabilities wiki space?Yes MUSIC Dublin Security/Vulnerabilityexisting code bases to be deprecated in this release
Have known vulnerabilities (critical and severe) to address/remove in the release been identified with JIRA ticket?Yes

MUSIC-289 - Getting issue details... STATUS

Create JIRA tickets

existing code bases to be deprecated in this release

Has the project committed to the release CII badging level?Yes

We will reach CII badging level of Silver

OPTFRA-421 - Getting issue details... STATUS


See https://www.coreinfrastructure.org/programs/badge-program/

or CII Badging Program

existing code bases to be deprecated in this release

Has the project created their project CII questionnaire and completed the ONAP level CII requirementsYeshttps://bestpractices.coreinfrastructure.org/en/projects/1722

See CII Badging Program

existing code bases to be deprecated in this release

If the project uses java, has the project integrated with the oparent.pom?Yes


existing code bases to be deprecated in this release

remaining test scripts use python

Product ManagementAre Product Backlog Epics entered in Jira?Yes

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

https://jira.onap.org/browse/MUSIC-199?jql=project%20%3D%20MUSIC%20AND%20issuetype%20%3D%20EpicCreate a Backlog item

Difference between a Product and Sprint Backlog

Are Product Backlog Stories entered in Jira?Yes

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Create a Backlog item
Are Product Backlog Stories linked to Product Backlog Epics?Yes

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Work in a Sprint
Are Product Backlog Stories prioritized?Yes

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Prioritize a Backlog item
Is the project team ready to estimate the top Stories (for coming Sprint) in Product backlog?Yes
Estimate a Backlog item
Is the project team ready to create a 2 weeks Sprint in Jira?Yes
Create a Sprint
Are Team Members willing to create Tasks and associate them with Stories in Jira?Yes
Create a Backlog item
Has the project team plan to contribute to Platform Maturity Improvement?NoMUSIC Dublin Release Planning#PlatformMaturity
Release ManagementIs there a Release Planning Template available and completed in wiki?YesMUSIC Dublin Release Planning
Has the Platform Maturity Table been updated with current status and Release goal?Yes
For each Release, there is a Platform Maturity table created for PTLs to record their goals and achievements at M4 (Example: Casablanca Release Platform Maturity).
Have all the "Release Components Name" been defined in Resources and Repositories for your project? (this includes all Sub-Components Names, Sub-Components Repositories Names, Maven Group ID, Sub-Components Description)YesResources and Repositories#MUSICResources and Repositories#MUSIC
Have all the "Resources committed to the Release" been defined in Resources and Repositories for your project? This includes First and Last names, LFID, Email Address and Location for PTL, Project Manager, Committers and Contributors.YesResources and Repositories#MUSIC
Have new developers made themself familiar on the Onboarding Process?Yes
Onboarding
Is the project team aware of the Release milestone? Any misses will required TSC exception.Yes

Integration and TestingHas the Integration Team defined the vendor equipment list?NALink to evidence
Has the Integration Team defined the End 2 End Release Test Case?NALink to evidence
Development



Is the Project Team committed to develop Unit Test?

Yes

Has the Project Team put in place an Automated Unit Test infrastructure?Yes

Is the Project Team committed to create Continuous System Integration Testing (CSIT) test case?Yes

Is the Project Team committed to perform Scrum ceremonies?Yes
Scrum Overview
Are the Project Team members aware of Continuous Integration Principles (don't break the build, Fix the build,...)?Yes
Continuous Integration
Has the Project Team a clear understanding on the Code Coverage expectations?Yes

Code Coverage and Static Code Analysis

Does the Project Team understand the Free and Open Source Software (FOSS) process?Yes
Free and Open Source Software
Is the Project Team willing to fill out accordingly the FOSS table?Yes
Fill out sub-pages for each project under Free and Open Source Software
Is the Project Team willing to comply to the Commit Process?Yes
Commit Messages
Does the Project Team understand the purpose of Code Review?Yes
Code Review
Is the Project Team aware of the Coding Guidelines?Yes
Development Practices (Jave Coding Style)