prometheus

Commit Graph

Author	SHA1	Message	Date
Ganesh Vernekar	04c1c7974e	Clarify the branch in preparing the release (#6122 ) Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>	5 years ago
Chris Marchbanks	f9ae1a7c2f	Add Chris Marchbanks as release shepherd for v2.14 (#5985 ) Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>	5 years ago
Frederic Branczyk	ac7b0ae4e6	RELEASE.md: Add command to run benchmark on release candidates Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com>	5 years ago
Frederic Branczyk	2914a537db	RELEASE.md: Add procedure for when to publish docs Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com>	5 years ago
Simon Pasquier	b3ecdd3f75	Bump promu to v0.5.0 It also includes an update of RELEASE.md since this version simplifies a bit the release process: promu will take care of drafting the GitHub release. Signed-off-by: Simon Pasquier <spasquie@redhat.com>	6 years ago
beorn7	2e77b32fb5	Further clarification Signed-off-by: beorn7 <beorn@grafana.com>	6 years ago
beorn7	1329faca14	Clarify when changes in master can be merged into the release branch Signed-off-by: beorn7 <beorn@grafana.com>	6 years ago
beorn7	adfc5aaa64	Update instructions for the release shepherd This codifies how 2.10 was released. It removes the inconsistency of freezing master for pre-releases but handling post-release bug fixes in a separate branch. The previous instructions came from a time where master was often in bad shape. However, that's a problem of its own, which should be avoided at all times and not only when a release is imminent. On other words, freezing master can still happen if it is in bad shape and we need a break from feature development and just fix the bugs for a while. However, it should not happen as a formal step during the release of a release candidate. On the contrary, a release candidate is not really a release candidate if we already know it is in such a bad shape that we need bug fixes. On the other hand, if we truly believe the RC could be identical to the final release, there is no need to freeze master. I can explain more of the concept if there is still a need for clarification. Signed-off-by: beorn7 <beorn@grafana.com>	6 years ago
beorn7	ac8d10f6e2	Replace Ganesh with Frederic for 2.11 Signed-off-by: beorn7 <beorn@grafana.com>	6 years ago
Julius Volz	1299a73781	Add next three release shepherds Signed-off-by: Julius Volz <julius.volz@gmail.com>	6 years ago
beorn7	bab26d9df8	Volunteer beorn7 as 2.10 release shepherd I'm willing to do this under the condition that I can run an experiment with never freezing master. See addition in the file. I believe, this way is more consistent with how we handle the bugfix releases after the final minor release is cut. It's at least worth a try. Signed-off-by: beorn7 <bjoern@rabenste.in>	6 years ago
Björn Rabenstein	81acc1dc0f	Update RELEASE.md to reflect mailing list change (#5472 ) We are not using `prometheus-users@googlegroups.com` for announcments anymore. Signed-off-by: Bjoern Rabenstein <bjoern@rabenste.in>	6 years ago
Brian Brazil	c8ee34d0b4	Put myself down for 2.9 release. Update docs on where to email release announcements. Signed-off-by: Brian Brazil <brian.brazil@robustperception.io>	6 years ago
Nguyen Van Duc	89d36a4bf6	Change http to https for security links (#5238 ) Signed-off-by: vanduc95 <ducnguyenvan.bk@gmail.com>	6 years ago
Ganesh Vernekar	ce69dcb0e5	Propose @codesome as 2.8 release shepherd Signed-off-by: Ganesh Vernekar <cs15btech11018@iith.ac.in>	6 years ago
Goutham Veeramachaneni	834adc9566	Propose myself as the 2.7 shepard Signed-off-by: Goutham Veeramachaneni <gouthamve@gmail.com>	6 years ago
Julius Volz	68f0787c37	Fix various misspellings of "shepherd" in the release docs (#5006 ) Signed-off-by: Julius Volz <julius.volz@gmail.com>	6 years ago
Frederic Branczyk	3274a74595	Add RELEASE.md Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com>	6 years ago

18 Commits (04c1c7974e2ef90752888fbfb8b8b9f6f2276c7c)