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.
Updated Release Shepherding (markdown)
add column for human-readable name on suggestion of Jessica Bian Li
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.
Added mention of Highlights and Breaking Changes to the work description
Edited text of link from "Release Notes Shepherd" to "Release Shepherd" to match the destination link, and the scope of the role.
Added Breaking Changes step after discussion with Tim Meehan
fix broken link to Release Notes Guidelines
Updated Release Notes Guidelines (markdown)
add link to Working with the Presto release notes PR
add "Working with the Presto release notes PR" summarizing my experience with the last eleven Presto releases as guidelines for others
add link to Presto-Open-Source-Community-Roles-&-Responsibilities#committers
add @yh.wang for 0.294
Add an example of external link to Formatting because many people write Markdown links in their PRs, release notes, and documentation
Add "Clear the CDN cache for `prestodb.io`. " per Slack discussion in #oss-prestodb-releases today with Li Zhuo.
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
Fix link for Release-Shepherding in Community Docs section
Updated Stable release process (every 2 months) (markdown)
Updated Committers (markdown)
add Zac Blanco