releases:brahmaputra:release_plan:vsperf_milestone_d_report
| Item | Question | Answer |
| 1 | If you have code are features frozen? | (Y) Feature development is now frozen |
| 2 | If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? | (Y) we are integrating with the opnfv-test-dashboard and this is now 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) |
| 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? | (Y) We will be working with Releng to integrate scripts with MaaS for vsperf testing |
| 5 | If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? | (Y) All our documentation is available through http://artifacts.opnfv.org/vswitchperf/docs/docs/index.html |
| 6 | List/describe your progress to date? | 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.) | Integration with MaaS, integration with Fuel, and nightly build in OPNFV |
| 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 |
releases/brahmaputra/release_plan/vsperf_milestone_d_report.txt · Last modified: 2015/11/30 13:52 by Maryam Tahhan
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
