Opening of Release Planning

• For existing Projects:
  • Every existing Beijing projects that plan to be part of Casablanca Release must email TSC to notify their intention through the ONAP TSC mailing list
• For New Projects:
  • New Candidate project must fill out “Project Proposal Template”
  • Post the proposal in the wiki at Proposed Projects
  • Inform ONAP TSC of their intention throught the ONAP TSC mailing list

By this date, all use cases/functional requirements need to be discussed with a different projects, and demanded scope of development should be clear to the projects:

For use cases/functional requirements:

• Template must be filled out

  https://wiki.onap.org/display/DW/Use+Case+Tracking+Template

(link to current use cases/functional requirements proposals description:

Release 4 (Dublin) Use Cases and functional requirements)

Last Date to announce Intention to Participate

This is the last date for TSC to formally approved New Project Proposal

Project Planning submission, by this date all projects have submitted in wiki their Release Planning materials.

That will give everyone to time to understand project scope and dependencies.

Planning process complete, all Project Deliverables are defined (including functional architecture, scope, dependencies,...)

Integration Team has defined the vendor Equipments list and the End 2 End Release Test Cases are fully defined.

The Document and Training teams have defined their plans. The packaging and installation strategy is defined.

To pass the M1 milestones, all approved projects have to:

1. Fill out the Release Planning Template
2. Fill out the Deliverables for Planning Milestone Checklist Template
3. Post these 2 project deliverables in wiki.

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.

API/data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen.

Any changes to the API must be brought to the knowledge of the TSC for review and approval.

50% of Functional Test Case are automated.

Code Freeze. Mark the end of the Features coding.

Jira issues are either fixed in the current release or assigned to next release.

100% of Functional Test Case are automated.

End 2 End Release Test Cases are implemented (Integration Team).

Release Candidate 0

RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

1. supporting integration testing (complete Health Check and Pair Wise Testing)
2. closing high priority defects
3. supporting Documentation team

Opening of Release Planning

• For existing Projects:
  • Every existing Beijing projects that plan to be part of Casablanca Release must email TSC to notify their intention through the ONAP TSC mailing list
• For New Projects:
  • New Candidate project must fill out “Project Proposal Template”
  • Post the proposal in the wiki at Proposed Projects
  • Inform ONAP TSC of their intention throught the ONAP TSC mailing list

Last Date to announce Intention to Participate

This is the last date for TSC to formally approved New Project Proposal

Project Planning submission, by this date all projects have submitted in wiki their Release Planning materials.

That will give everyone to time to understand project scope and dependencies.

Planning process complete, all Project Deliverables are defined (including functional architecture, scope, dependencies,...)

Integration Team has defined the vendor Equipments list and the End 2 End Release Test Cases are fully defined.

The Document and Training teams have defined their plans. The packaging and installation strategy is defined.

To pass the M1 milestones, all approved projects have to:

1. Fill out the Release Planning Template
2. Fill out the Deliverables for Planning Milestone Checklist Template
3. Post these 2 project deliverables in wiki.

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.

API/data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen.

Any changes to the API must be brought to the knowledge of the TSC for review and approval.

50% of Functional Test Case are automated.

Code Freeze. Mark the end of the Features coding.

Jira issues are either fixed in the current release or assigned to next release.

100% of Functional Test Case are automated.

End 2 End Release Test Cases are implemented (Integration Team).

Release Candidate 0

RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

1. supporting integration testing (complete Health Check and Pair Wise Testing)
2. closing high priority defects
3. supporting Documentation team

Nov 08, 2018

Nov 27, 2018

Release Candidate 2

TSC decision on Nov 8 to postpone RC2 to Nov 27.

Nov 15, 2018

Nov 30, 2018

Casablanca Release Sign-Off

TSC decision on Nov 8 to postpone Sign-Off to Nov 30.

Opening of Release Planning

• For existing Projects:
  • Every existing Amsterdam projects that plan to be part of Beijing Release must email TSC to notify their intention through the ONAP TSC mailing list
• For New Projects:
  • New Candidate project must fill out “Project Proposal Template”
  • Post the proposal in the wiki at Proposed Projects
  • Inform ONAP TSC of their intention throught the ONAP TSC mailing list

Last Date to announce Intention to Participate

This is the last date for TSC to formally approved New Project Proposal

Project Planning submission, by this date all projects have submitted in wiki their Release Planning materials.

That will give everyone to time to understand project scope and dependencies.

Planning process complete, all Project Deliverables are defined (including functional architecture, scope, dependencies,...)

Integration Team has defined the vendor Equipments list and the End 2 End Release Test Cases are fully defined.

The Document and Training teams have defined their plans. The packaging and installation strategy is defined.

To pass the M1 milestones, all approved projects have to:

1. Fill out the Release Planning Template
2. Fill out the Deliverables for Planning Milestone Checklist Template
3. Post these 2 project deliverables in wiki.

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.

API/data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen.

Any changes to the API must be brought to the knowledge of the TSC for review and approval.

50% of Functional Test Case are automated.

Code Freeze. Mark the end of the Features coding.

Jira issues are either fixed in the current release or assigned to next release.

100% of Functional Test Case are automated.

End 2 End Release Test Cases are implemented (Integration Team).

Release Candidate 0

RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

1. supporting integration testing
2. closing high priority defects
3. supporting Documentation team

May 17, 2018

May 31, 2018

Release Candidate 2

TSC decision to postpone RC2 review by 2 weeks (Topic 3, section am)

May 24, 2018

June 7, 2018

Beijing Release Sign-Off

TSC decision to postpone RC2 review by 2 weeks (Topic 3, section am)

All projects candidate for the first ONAP Release have to:

1. use the Project Proposal Template
2. post the proposal in the wiki at Proposed Projects
3. inform ONAP TSC of their intention throught the ONAP TSC mailing list.

Planning process complete, all Project Deliverables are defined (including functional architecture, scope, dependencies,...)

Integration Team has defined the vendor Equipments list and the End 2 End Release Test Cases are fully defined.

The Document and Training teams have defined their plans. The packaging and installation strategy is defined.

To pass the M1 milestones, all approved projects have to:

1. Fill out the Release Planning Template
2. Fill out the Deliverables for Planning Milestone Checklist Template
3. Post these 2 project deliverables in wiki.

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.

API/data model freeze. Mark the end of API and Data Model change. API and Data Model are now Frozen.

Any changes to the API must be brought to the knowledge of the TSC for review and approval.

50% of Functional Test Case are automated.

Code Freeze. Mark the end of the Features coding.

Jira issues are either fixed in the current release or assigned to next release.

100% of Functional Test Case are automated.

End 2 End Release Test Cases are implemented (Integration Team).

Release Candidate 0

RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

Project Team focused its effort on:

1. supporting integration testing
2. closing high priority defects
3. supporting Documentation team