You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

As Juniper announced that they are already close to M4 while Tungsten Fabric formally is in M0 we propose to review 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/tasks in proper sub-project (TF Core, TF Operator)
  4. Technical design documentation stored in https://github.com/tungstenfabric/tf-specs repo in R2011/TFF-XX subfolder - link provided in Jira Epic ticket
  5. All additional necessary documentation stored as well in the same folder (API specification, installation guide, user manual, demo, instruction, etc)
  6. Documentation presented and discussed on TF meeting - approved by relevant module committers and Documentation PTL 
  7. Feature tests conducted, test report provided (report or documentation stored in TF repo) 
  8. Tests results presented, discussed with TF Community (to assure proper QA coverage)
  9. branch of code marked (linked to TFF Jira ticket)


Move from M0, M1, M2, M3 → M4

Requirement
Documentation
  • Link to API documentation added to JIRA EPIC
  • Link to CLI documentation added to JIRA EPIC
  • Link to Blueprint added to JIRA EPIC
  • Link to Tech spec added to JIRA EPIC
  • Link to Installation documentation added to JIRA EPIC
  • Link to Deployment documentation added to JIRA EPIC
  • Link to user manual  added to JIRA EPIC
Tests
  • Link to a manual test procedure added to JIRA EPIC
  • Link to a code of automated tests added to JIRA EPIC  

Move from M4 → Release candidate

Requirement
Documentation
  • Blueprint is added to github/tf-spec 
  • Tech spec is added to github/tf-spec 
  • API documentation written in markdown is attached to JIRA EPIC 
  • CLI documentation written in markdown is attached to JIRA EPIC
  • Installation documentation  written in markdown is attached to JIRA EPIC
  • Deployment documentation written in markdown is attached to JIRA EPIC
  • user manual written in markdown is attached to JIRA EPIC
  • All above points are confirmed by Documentation project PTL
Tests
  • none
  • No labels