Hi everyone, I want to bring up the idea of having a retrospective on the release from the release manager's perspective. The idea would be to collect feedback on what went well and what could be improved for a specific minor release. So far, I didn't find anything on that topic. Does the community find this useful? Or was this already done but not helpful?
I see three options here: 1. Having an actual meeting where issues can be discussed and/or experiences can be shared between the release managers of the previous release and the release managers of the next minor release. Of course, this could be open to other contributors as well. A summary could be provided in the Flink wiki (the Flink release's wiki article). 2. The release manager(s) provide a summary on the Flink release's wiki article as part of the release process. 3. Leave the process as is without any additional retrospective but focus on improving the documentation if issues arose during the release. That might help people who consider contributing to the community through supporting the release efforts. Additionally, it might help in understanding what went wrong in past releases retroactively (e.g. the longer release cycle for 1.15). I'm curious about opinion's on that topic. Best, Matthias