Mirrors
/
flux2
mirror of https://github.com/fluxcd/flux2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: Mention Flux upgrade guide in release notes

Browse Source 
See https://github.com/fluxcd/flux2/discussions/5072

Signed-off-by: Mateusz Łoskot <mateusz@loskot.net>
pull/5073/head
Mateusz Łoskot 2 months ago committed by GitHub
parent 5b83111dc6
commit 995e1dcc32
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File

5
docs/release/release-notes-template.md
Unescape Escape View File

@ -43,6 +43,9 @@ The following template can be used for the GitHub release page:
<!-- auto-generated list of pull requests to the CLI starts here --> <!-- auto-generated list of pull requests to the CLI starts here -->
``` ```
Typically, you want to link the [Flux upgrade](https://fluxcd.io/flux/installation/upgrade/)
guide to refer users for up to date information on upgrade options.
In some scenarios, you may want to include specific information about API In some scenarios, you may want to include specific information about API
changes and/or upgrade procedures. Consult [the formatting of changes and/or upgrade procedures. Consult [the formatting of
`v2.0.0-rc.1`](https://github.com/fluxcd/flux2/releases/tag/v2.0.0-rc.1) for `v2.0.0-rc.1`](https://github.com/fluxcd/flux2/releases/tag/v2.0.0-rc.1) for
@ -69,4 +72,4 @@ The following template can be used for the Slack release message:
``` ```
For more concrete examples, see the pinned messages in the [Flux Slack For more concrete examples, see the pinned messages in the [Flux Slack
channel](https://cloud-native.slack.com/archives/CLAJ40HV3). channel](https://cloud-native.slack.com/archives/CLAJ40HV3).

Write Preview
Loading…
Cancel
Save