...
Background
This retro is for the S74: XXXXXXXXXXXXXXXXX???? 3.5.0 Release
Please add comments before the meeting! We’ll take a few minutes to add additional comments and discuss, then put together action items to operationalize suggestions.
...
Start doing | Stop doing | Keep doing | Shout outs |
|---|
Being more proactive around making tech debt and bugfixing part of every sprint planning on top of having specific bugfixing/tech debt weeks Doing continuous translations rather than a massive list at the end of the sprint. (Loic) More specific process for translations? What happened to post-release vacation? (I never heard of post-release vacation?  ) I would like to get involved in non-sensitive styling issues - ie: SASS or CSS (Loic).
| | 2 week release cycle!! Post release patch (they are easy, and fun – and the alternative is stricter code freeze) I want to validate all visual and user sensitive tickets (Loic) Dev control of the release process / checklist One day a week of plain focus. One reviewer per PR. Paid testers.
| I would like to say a huge thank you to the whole team for their support. Especially to Antonella for all her efforts to help me learn JavaScript. Anto Sgarlatta for leading our smoothest release process yet! (And also to patch team – we did really well too!) All the team for doing great work 
|
Action items:
- Review previous retro action items
-
- Make sure each sprint has a few tech debt tickets, even when the focus of the sprint is feature development Anto Sgarlatta