We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Added if an upgrade is not prompted by a CVE then NO RELEASE NOTE is correct, formatted the Phrasing topic for better readability.
Add link example in Formatting for Presto C++ Session Properties.
Updated Release Notes Guidelines (markdown)
add link to Working with the Presto release notes PR
Add an example of external link to Formatting because many people write Markdown links in their PRs, release notes, and documentation
Added "link to documentation whenever possible" in Phrasing, and added "Changes" to the section heading examples in the Order of sections.
Updated JDBC to JDBC Driver in Order of sections to follow the automated test.
adding Router section heading following discussion with Tim Meehan
add Plugin to the Order of sections as a result of work on https://github.com/prestodb/presto/pull/24855
Edited to remove "add PR link" instructions as https://github.com/prestodb/presto/pull/24354 automatically does that now
Add "CVE-prompted PRs should link to the CVE in the release note", with an example, in Phrasing.
Add example of ref linking to heading within page from PR 23886
Clarify the order of changes section
add the new pull request number in the release notes entry
Update Release Notes example to include Connector in Hive Changes header as described in Section naming
Added Audience topic capturing @tdcmeehan comment on PR 21579, and and Documentation-only Pull Request topic based on previous discussions