User Tools

Site Tools


releases:brahmaputra:release_plan:pharos_milestone_d_report

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
releases:brahmaputra:release_plan:pharos_milestone_d_report [2015/11/24 23:10]
Debra Scott created
releases:brahmaputra:release_plan:pharos_milestone_d_report [2015/12/01 06:48] (current)
Trevor Cooper
Line 2: Line 2:
  
 1. If you have code are features frozen? y/n/na 1. If you have code are features frozen? y/n/na
 +na
  
 2. If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? y/n/na 2. If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? y/n/na
 +Pharos provides lab infrastructure for development,​ integration for feature and test projects. Test dashboard API is being handled by functest. Configuration templates may be considered as "​APIs"​ for deployment tool projects, these have not been frozen.  ​
  
 3. Are your test specifications frozen and provided to test projects? No additional use cases can be added to the release after this milestone (ie. feature projects have added the test cases for their project to the test team suite) y/n/na 3. Are your test specifications frozen and provided to test projects? No additional use cases can be added to the release after this milestone (ie. feature projects have added the test cases for their project to the test team suite) y/n/na
 +na
  
 4. If you require post-install processing have you consulted with CI (Octopus), CD (Releng), and/or companion test projects (functest, yardstick, etc) regarding scripts you may need to provide such as for install, set-env, run-test, clean-env? 4. If you require post-install processing have you consulted with CI (Octopus), CD (Releng), and/or companion test projects (functest, yardstick, etc) regarding scripts you may need to provide such as for install, set-env, run-test, clean-env?
 +Working with CI and CD
  
 5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? y/n/na 5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? y/n/na
 +na
  
 6. List/​describe your progress to date? 6. List/​describe your progress to date?
 +We have an accurate map of lab resources and what they are being used for. Additional lab resources have been assigned for projects that have documented their needs (although not all the assigned resources are available to projects yet). A Jenkins instance for "​project CI" (build system) is being configured by LF.  ​
  
 7. Describe what you have remaining to do? (hint: You should only have completion of existing features and bug fixes to do. For test projects you will be developing remaining tests according to frozen specifications.) 7. Describe what you have remaining to do? (hint: You should only have completion of existing features and bug fixes to do. For test projects you will be developing remaining tests according to frozen specifications.)
 +  * Complete MAAS Pilot
 +  * Machine and human readable templates
 +  * Need training for volunteers to support for LF infrastructure
 +  * Help all labs to be Pharos compliant
 +  * Some labs while available still need to publish developer access process and guides
 +  * Some labs are not yet setup under Jenkins control
  
 8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/​Yellow/​Red 8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/​Yellow/​Red
 +Yellow
  
 9. List any serious or blocking issues that are impeding progress on your project: 9. List any serious or blocking issues that are impeding progress on your project:
 +Lab owners need to provide resources for Pharos
releases/brahmaputra/release_plan/pharos_milestone_d_report.1448406637.txt.gz · Last modified: 2015/11/24 23:10 by Debra Scott