Honeysuckle - retrospective notes
Technical Leads Q3 2020 Release retrospective
Action Items
| # | Area | Status | Description | Next steps |
|---|---|---|---|---|
| 1 | Rancher | PENDING | We need to decide how to use large data set and ask this question to CAP team | Discussion is required |
| 2 | Technical | IN PROGRESS | Apply Spring instead of RMB to reduce RMB dependency | |
| 3 | Quality | IN PROGRESS | Test automation could help to reduce lead time | Create integration tests coverage |
| 4 | Process | PENDING | Conduct separate discussion around platform changes to answer on question: How often platform should be released and how to reduce lead time | Discussion is required |
| 5 | Monitoring & control | OBSERVATION | Don't make breaking changes at the end of release cycle | |
| 6 | Monitoring & control | PENDING | Conduct separate discussion: How can we notice that modules have not been released during the release process? | to schedule session |
| 7 | Process | PENDING | Make fix version required field | |
| 8 | Process | IN PROGRESS | Review possibility of automation of release process and simplify it. | Working on automation for interfaces gathering |
| 9 | Monitoring & control | IN PROGRESS | Setup notification for "Awaiting release" status to notify module owners about tickets that need to be release | |
| 10 | Process | PENDING | Add policy around changes that could be included in modules versions after release deadline | |
| 11 | Monitoring & control | Prepare stats on percent of changes in each app/module from release to release |