...
The milestones are defined by the Documentation subcommittee.
Blueprint Validation Project reporting
BP validation projects milestones will be different in the 'Incubation' and 'Mature' stages since the graduation criteria from these two stages are different.
...
Each BP validation project's PTL is responsibility for updating the Incubation or Mature BP tracking tables for their BP validation project so that the TSC can easily track all BP validation projects' status.
In addition to the PTLs reporting the actual dates each milestone is achieved, the PTLs are encouraged in their planning stage to enter their target date for each milestone in the same table.
Feature Project reporting
Each feature project's PTL is responsibility for the updating feature project tracking tables table for their feature project so that the TSC can easily track all feature projects' status.
Blueprint
...
Core stage reporting
MBC = Milestone Bp Core
1) Entry Criteria: The project is graduated by the TSC from Mature to Core after TSC review and approval (Akraino Project Reviews).
DO WE WANT TO CONDUCT MBC PROJECT REVIEWS IN CORE STATE (AS THERE'S NO WHERE TO GO!)? OR RATHER HANDOVER PROJECT REPORTING TO THE PROJECT'S WIKI PAGE (FEATURES ADDED, BUGS etc)
Feature Project reporting
MF = Milestone Feature
REMOVE THE RC STAGES AS THIS IS A WATER FALL MODEL
...
Project Name
...
MF0 Kick-Off
...
MF1
Planning
...
MF2
Functionality freeze
...
MF3
API Freeze
...
MF4
Code Freeze
...
RC0
Release Candidate 0
...
RC1
Release Candidate 1
...
RC2
Release Candidate 2
...
Sign-Off
Release Delivery
...
...
...
...
...
Projects R4 API Information Reporting Requirements
Starting with R4, all blueprint projects are required to report significant edge computing APIs they both expose and consume. The API Subcommittee page has instructions.