Hi all, Currently the release notes are a plain export of the JIRA tickets that were resolved in a certain version. Although it is convenient and easy to generate by the release manager it usually lacks information about breaking/behavior changes, deprecation notices, and appropriate documentation entry points for new features and major improvements.
In order to create a better user experience, I was thinking that it would be nice to have curated release notes so that end-users can get better insights on what's coming with every release. Concretely, I was thinking of having a new directory in the hive-site repo (content/releases) and have a dedicated page for each ongoing release (4-1-0-release-notes.md) that we should enrich incrementally after resolving an *important* JIRA ticket that requires further communication. By important, I refer mostly to big features/improvements, breaking/behavior changes, and deprecation notices. It remains at the committers/reviewer/release manager discretion to judge what needs to go there and what not. Consider for example HIVE-27831 [1], that just landed on master. This changes the default value of a property thus it would be nice if the end-users are aware. How do people feel about this proposal? Best, Stamatis [1] https://issues.apache.org/jira/browse/HIVE-27831
