...
- Review previous retro’s action items
- SPIKE on the depth of navigation issues . (See
)Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-4022 - Update from React router version 4 to 5 or 6? Anto says there are guides on how major versions will change. Will probably be a mix of issues known a priori and those found afterwards. Need to bump our React version too? No! (See
)Jira Legacy server System JIRA serverId 815f41e5-e5fb-3402-8587-82eccc3ffab0 key LF-4021 - Look into Jira: is there a way to calculate and track the portion of time spent on feature vs tech debt Anto Sgarlatta
- Make sure each sprint has a few tech debt tickets, even when the focus of the sprint is feature development Anto Sgarlatta
- Anto Sgarlatta to discuss current implementation of app styling with Loic Sans during next 1-on-1
- Begin a Confluence doc on things you want to learn and things you’re interested in teaching and then schedule sessions around them Anto Sgarlatta
- Lite Farm to schedule a team discussion on the appropriate mechanisms for verifying a release will be successful (e.g. bug free)
- Denis Dovganyuk to begin labeling bugs with “Inconsistently reproducibility”
- Investigate automating the addition of a release tag based on the current version number (e.g. “3.7.x”) to a ticket when moving it into “Resolved” or “Release Ready” Anto Sgarlatta
...