1. Project name Releng
2. Project status indicator for milestone C readiness: Green/Yellow/Red; GREEN = on track; YELLOW = working minor issues to get back on track; RED = offtrack with major issues Green
3.Name of person providing status Fatih Degirmenci
4.a link to your Jira tasks (filtered on R2) https://jira.opnfv.org/issues/?filter=10607
5. a link to your Jira dashboard https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10607 (Kanban board: https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=13)
6.a statement of your progress at linking cross project dependencies in Jira Releng project has dependencies towards projects listed below.
Pharos for hardware/lab resources, dashboard, booking system. Octopus for CI pipeline descriptions and processes. Functest and Yardstick for test result reporting/dashboard implementation. There are implicit dependencies towards Genesis, Installer projects, and projects that produce artifacts that are going to be integrated into CI. These dependencies are not visible as of yet since they are still in progress by Genesis project so they have not been linked as dependencies to Releng.
7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) Ready. 4 Epics and Stories under these Epics have been identified. Development work has already been started.
8.a statement of your readiness (high level planning complete & in Jira) for future sprints Ready. Releng does not work in Scrum so no sprints defined.
9.a statement about any issues you have Lack of hardware resources.
10.how & when you will finish getting your tasks & dependencies into Jira if not complete Backlog in Jira is ready.
11.how and when you will get ready to start development for Brahmaputra if not ready now Ready. Development work has already been started.
12.a statement summarizing your project risk analysis & planning status Pharos and Octopus projects have high impacts on Releng so any delay in the these projects will risk Releng for progressing further. Apart from the explicit dependencies listed above, the high number of Brahmaputra participating projects and the late requests that might arrive from these projects have potential to increase the risk. Needs that might arise from the projects that produce artifacts, Genesis, and Installer projects also have high impact on Releng when it comes to automation/integration effort.