releases:brahmaputra:release_plan:policytest_milestone_d_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:policytest_milestone_d_report [2015/11/24 23:12] Debra Scott created |
releases:brahmaputra:release_plan:policytest_milestone_d_report [2015/12/08 18:04] (current) Brady Johnson |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Policy Test Milestone D Report | Policy Test Milestone D Report | ||
| - | 1. If you have code are features 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 | + | |Item|Question|Answer| |
| + | |1 | If you have code are features frozen? | (Y) The Upstream ODL GBP project scope was frozen in Milestone M3 on October 15, 2015. | | ||
| + | |2 | If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? | (N) There are no OPNFV PolicyTest APIs used by other projects. | | ||
| + | |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) ETA December 9, 2015. The Yardstick and Functest projects have been informed that we're running a bit behind schedule, and have agreed to allow us to submit our test cases on the ETA.| | ||
| + | |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?| (N) No post processing needed. | | ||
| + | |5 | If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? | (NA) | | ||
| + | |6 | List/describe your progress to date? | Keith, fill this part in.| | ||
| + | |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.)| Keith, fill this part in. | | ||
| + | |8 | How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red| Keith, fill this part in. | | ||
| + | |9 | List any serious or blocking issues that are impeding progress on your project| Keith, fill this part in.| | ||
| - | 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 | ||
| - | |||
| - | 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? | ||
| - | |||
| - | 5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? y/n/na | ||
| - | |||
| - | 6. List/describe your progress to date? | ||
| - | |||
| - | 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.) | ||
| - | |||
| - | 8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red | ||
| - | |||
| - | 9. List any serious or blocking issues that are impeding progress on your project: | ||
releases/brahmaputra/release_plan/policytest_milestone_d_report.1448406720.txt.gz · Last modified: 2015/11/24 23:12 by Debra Scott
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
