releases:brahmaputra:release_plan:sfqm_milestone_d_report
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:sfqm_milestone_d_report [2015/11/30 09:29] Maryam Tahhan |
releases:brahmaputra:release_plan:sfqm_milestone_d_report [2015/11/30 13:43] (current) Maryam Tahhan [Table] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| SFQM Milestone D Report | SFQM Milestone D Report | ||
| - | ^ ^ ^ | + | | Item | Question | Answer | |
| - | |1. If you have code are features frozen? y/n/na | Yes they are frozen, pushed and merged in DPDK. They will be part of DPDK 2.2. | | + | | 1 | If you have code are features frozen? | (Y) All features are complete and upstreamed to DPDK, they will be part of DPDK 2.2 | |
| - | | | | | + | | 2 | If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? | (N/A) | |
| + | | 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) | (N/A) | | ||
| + | | 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/A) | | ||
| + | | 5 | If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? | (Y) All documentation is complete and upstreamed to DPDK, it will be part of DPDK 2.2 | | ||
| + | | 6 | List/describe your progress to date? | Project is on track | | ||
| + | | 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.) | updating the collectd integration for release B if the appropriate features are in place in DPDK 2.3 | | ||
| + | | 8 | How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red | Green | | ||
| + | | 9 | List any serious or blocking issues that are impeding progress on your project | None | | ||
| - | |||
| - | 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 | ||
| - | |||
| - | 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/sfqm_milestone_d_report.1448875767.txt.gz · Last modified: 2015/11/30 09:29 by Maryam Tahhan
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
