...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
| Date | Project | Deliverable |
|---|---|---|
| 1/8/18 | VNF Requirments | Draft M1 Project Plan available on VNFRQTS Project Wiki |
| 1/18/18 | VNF Requirments | ONAP Beijing M1 Milestone - planning process complete |
| 2/12/18 | VNF Requirments | ONAP Beijing M2 Milestone - functionality freeze |
| 3/8/18 | VNF Requirments | ONAP Beijing M3 Milestone - API data model freeze |
| 3/29/18 | VNF Requirments | ONAP Beijing M4 Milestone - code freeze |
| 4/19/18 | VNF Requirments | ONAP Beijing RC0 Milestone |
| 5/3/18 | VNF Requirments | ONAP Beijing RC1 Milestone |
| 5/17/18 | VNF Requirments | ONAP Beijing RC2 Milestone |
| 5/24/18 | VNF Requirments | ONAP Beijing Signoff Milestone |
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
...