mirror of
https://github.com/prometheus/prometheus.git
synced 2024-12-24 21:24:05 -08:00
Merge pull request #10110 from prometheus/beorn7/release2
release: Extend instructions for the release shepherd
This commit is contained in:
commit
366cba876d
|
@ -72,7 +72,7 @@ If a bug fix got accidentally merged into main after non-bug-fix changes in main
|
|||
|
||||
Maintaining the release branches for older minor releases happens on a best effort basis.
|
||||
|
||||
### 0. Updating dependencies
|
||||
### 0. Updating dependencies and promoting/demoting experimental features
|
||||
|
||||
A few days before a major or minor release, consider updating the dependencies.
|
||||
|
||||
|
@ -87,6 +87,10 @@ you can skip the dependency update or only update select dependencies. In such a
|
|||
case, you have to create an issue or pull request in the GitHub project for
|
||||
later follow-up.
|
||||
|
||||
This is also a good time to consider any experimental features and feature
|
||||
flags for promotion to stable or for deprecation or ultimately removal. Do any
|
||||
of these in pull requests, one per feature.
|
||||
|
||||
#### Updating Go dependencies
|
||||
|
||||
```
|
||||
|
@ -157,3 +161,5 @@ For release candidate versions (`v2.16.0-rc.0`), run the benchmark for 3 days us
|
|||
If the release has happened in the latest release branch, merge the changes into main.
|
||||
|
||||
Once the binaries have been uploaded, announce the release on `prometheus-announce@googlegroups.com`. (Please do not use `prometheus-users@googlegroups.com` for announcements anymore.) Check out previous announcement mails for inspiration.
|
||||
|
||||
Finally, in case there is no release shepherd listed for the next release yet, find a volunteer.
|
||||
|
|
Loading…
Reference in a new issue