Mark-Simulacrum
commented
3 years ago Hm, so I feel like maybe a good fit might be:
- We make a point to bring up any problems noted with release process week after release (so there's 8 days after release at current Friday meeting slot).
- Anything brought up that isn't immediately resolvable (e.g., something like "forgot to cherry pick release notes" could be resolved with "edit docs to include an explicit step, as was done 10ish cycles back I think) we go to async via filing an issue
Does that feel right/good to you?
XAMPPRocky
Every six weeks we cut and deploy a new release of Rust. This is sometimes harder to pull off than others, because of the nature of some changes in those releases or real world factors. I think we should try dedicating some time in either the next meeting after the release or the week after that, to reflect on how people felt about how the release went.
I'm proposing this as a synchronous meeting topic as opposed to opening an issue, because I do feel most of the time releases go pretty well, and I don't know there won't be enough to say to warrant adding another issue that someone has to remember to open and close regularly.