Hi All, A small discussion to have where I would like your input is to add a file to the root of the repository to highlight the most important changes for each release. Currently it is the work of the Release manager to sift through our tickets and try to create a comprehensive list of the key changes for each release. This causes useful changes to slip through the cracks...
While we do always generate release notes in our GitHub releases I find that list to be not too user friendly. It's often a bit too technical. It usually also does not translate to a great starting point for the release blog post. I see 2 paths we could follow. 1. Add a release notes or changes document to our repository (examples [1][2]) 2. Put a bit more effort in making our PR messages more clear, as you can see in our notes[3] a lot of those lines are either not user friendly or technical things that the user doesn't care about. Let me know what you think, Cheers, Hans [1] https://github.com/apache/beam/blob/master/CHANGES.md [2] https://github.com/apache/airflow/blob/main/RELEASE_NOTES.rst [3] https://github.com/apache/hop/releases/tag/2.16.0-rc1
