As Juniper announced that they are already close to M4 while Tungsten Fabric formally is in M0 we propose to review bellow the below points to assure that TF may confirm M4 achievement.

1. Blueprint stored as Confluence page or md file in https://github.com/tungstenfabric/tf-specs repo linked to TFF-XX relevant Jira epic ticket
2. All dependencies between existing functionality and requested change/feature discussed and agreed by PTL and related approvers (based on Modules/Commiters)
3. Jira Epic ticket updated with overall development plan information or broken down into stories in related Jira /tasks in proper sub-project (backlogTF Core, plan) - presented and discussed on TWS meetingThe final version of Blueprints, Release Scope and Release Plans for participating projects discussed and approved by approversTF Operator)
4. Technical design fully provided, agreed (documentation on the Confluence/github/tf-spec available)
5. Jira Epic ticket updated with link to technical design
6. Feature tests started
7. Feature/Functionality Freeze - Technical Design approved by relevant approvers (Modules/Commiters)
8. External API available for beta-tests
9. Jira Epic ticket updated with information about API availability (documentation link - tf repo)
10. Documentation in progress
11. Tests in progress
12. API Freeze confirmed by Feature Lead (comment on Jira Epic ticket with repo/commit ID link)
13. all functionality and APIs available for testing
14. Jira Epic ticket updated with information about final API documentation, executed UI tests documentation
15. Documentation provided - confirmed by Documentation project PTL
16. documentation stored in https://github.com/tungstenfabric/tf-specs repo in R2011/TFF-XX subfolder - link provided in Jira Epic ticket
17. All additional necessary documentation stored as well in the same folder (API specification, installation guide, user manual, demo, instruction, etc)
18. Documentation presented and discussed on TF meeting - approved by relevant module committers and Documentation PTL 
19. Feature tests conducted, test report provided (report or documentation stored in TF repo) 
20. Tests results presented, discussed with TF Community (to assure proper QA coverage)
21. branch of code marked (linked to TFF Jira ticket)Code freeze confirmed by Feature Lead (comment on Jira Epic ticket) - only bug fixing allowed

Move from M0, M1, M2, M3 → M4

...