make a post-mortem forllowing the YEC 2023 launch
just a ticket to keep track of issues we find during the YEC 2023 launch today
-
blog!228 (merged) was merged without review, and prior to when @lavamind and @mattlav were around to handle the actual launch -
tor browser start announcing the launch before the time as well -
TPA (@anarcat) postponed the launch from "midnight UTC" to "morning America/Eastern" without proper coordination -
translation strings were sent to @emmapeel too late -
the donate website is under documented, a total mess, and hard to test -
specifically, it was believed it was not possible to test the donation workflow in staging
This is not to lay blame on anyone, nor to divert us from the YEC. Those are issues we can look at much later.
ideas for future improvements:
- organize the timeline on GitLab milestones and issues (or at least Nextcloud) instead of a private Google Docs, and keep tickets up to date with progress
- have a point person responsible for technical coordination that's available for the week before launch, during launch, and after launch
- ensure testing is performed long before launch
- ensure translations are ready before launch
- ensure donate.tpo is up to date before sending announcements
- document deployment workflows properly
- communicate clearly, to all stakeholders, when a blocker occurs
Edited by pavel