From 5141e7743880ad34708804541d3b32969b97d788 Mon Sep 17 00:00:00 2001 From: Yuya Ebihara Date: Wed, 8 Apr 2026 11:58:46 +0900 Subject: [PATCH] Add `Breaking changes` to release note order --- development/process.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/development/process.md b/development/process.md index c678eb891c..7b47743a2f 100644 --- a/development/process.md +++ b/development/process.md @@ -190,10 +190,11 @@ For example, Trino release are ordered following the In each section different release notes entries are sorted: -1. **New features**: Start with `Add` or `Add support for` or similar wording -2. **Performance improvements**: Start with `Improve` or `Improve performance` +1. **Breaking changes**: Start with `{{breaking}}` +2. **New features**: Start with `Add` or `Add support for` or similar wording +3. **Performance improvements**: Start with `Improve` or `Improve performance` or similar wording -3. **Bug fixes**: Start with `Fix` or `Prevent` or similar wording +4. **Bug fixes**: Start with `Fix` or `Prevent` or similar wording Use [imperative present tense, as used in a command or request](https://en.wikipedia.org/wiki/Imperative_mood) to describe the change.