Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
Octopus Milestone D Report

1. If you have code are features frozen? 
  * na

2. If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? 
  * yes

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) 
  * 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? 
  * na

5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? 
  * yes. Documents exist from Arno release and need some updates.

6. List/describe your progress to date?
  * CI pipelines up as far as requested by projects.

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.)
  * Some projects still will setup their pipelines. 
  * Octopus has to prepare the final release testing

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:
  * It might be challenging if projects come late and have special requirements on CI pipeline. Risk: Low
  * If all release testing must be done on LF PODs, this will take long execution time. Risk: High. We are already working on a proposal.
Wiki

User Tools

Site Tools

Page Tools
