This shows you the differences between two versions of the page.
— |
octopus_milestone_c_report [2015/09/28 21:50] (current) Debra Scott created |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | 1.Project name: Octopus | ||
+ | |||
+ | 2.Project status indicator for milestone C readiness: Green | ||
+ | |||
+ | 3.Name of person providing status: Ulrich Kleber | ||
+ | |||
+ | 4.a link to your Jira tasks (filtered on R2), https://jira.opnfv.org/i#issues/?jql=project%20%3D%20OCTO%20AND%20labels%20%3D%20R2 | ||
+ | |||
+ | 5.a link to your Jira dashboard: https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10603 | ||
+ | |||
+ | 6.a statement of your progress at linking cross project dependencies in Jira: Octopus needs to setup CI pipeline for all Brahmaputra projects. These are covered by OCTO-133 epic. Currently 5 projects have stories in this epic. Dependency on the other projects is not critical, since we know the amount of work. | ||
+ | |||
+ | 7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile): Seven R2 stories in progress. | ||
+ | |||
+ | 8.a statement of your readiness (high level planning complete & in Jira) for future sprints: high level planning complete & in Jira | ||
+ | |||
+ | 9.a statement about any issues you have: The number of Jenkins jobs will increase, so CI needs to use community labs. Work in progress. | ||
+ | |||
+ | 10.how & when you will finish getting your tasks & dependencies into Jira if not complete n/a | ||
+ | |||
+ | 11.how and when you will get ready to start development for Brahmaputra if not ready now n/a | ||
+ | |||
+ | 12.a statement summarizing your project risk analysis & planning status. Milestone-C-Ready. | ||