IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-11-24 09:50:29 -06:00
Code Issues Packages Projects Releases Wiki Activity

Docs: Minor docs update

Browse Source
This commit is contained in:
Torkel Ödegaard 2020-11-10 12:14:02 +01:00 committed by GitHub
parent f220f3b5f9
commit 2e5588f455
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
WORKFLOW.md
View File

@ -42,7 +42,7 @@ Once a PR is approved as per above, any team member MAY merge the PR.
PRs intended for inclusion in the next PATCH release they must be backported to the release branch. The bot can do this automatically. [Read more on backport PRs](https://github.com/grafana/grafana/blob/master/.github/bot.md). Both the source PR and the backport PR should be assigned to the patch release milestone, unless you are backporting to many releases then it can differ. PRs intended for inclusion in the next PATCH release they must be backported to the release branch. The bot can do this automatically. [Read more on backport PRs](https://github.com/grafana/grafana/blob/master/.github/bot.md). Both the source PR and the backport PR should be assigned to the patch release milestone, unless you are backporting to many releases then it can differ.
This backport process is also needed during a beta period to get fixes into the stable release. Backport PRs are also needed during the beta period to get fixes into the stable release.
# Release workflow # Release workflow