Prometheus 3.0 release coordination
summary
Coordinators organize Prometheus 3.0 using a GitHub Projects board with labels, a shared release branch and manual change lock PRs to collect release notes; most of the coordinators are outside the core Prometheus team and the group size is larger than past releases. The board makes status and newcomer tasks visible, several coordinators submit actual code, the beta ships on schedule, and automation for gathering release notes is proposed to replace the manual merge and branch maintenance.
AI-written summary · about
related talks
25mPrometheus Governance 2.0: A Case-study in Evolving the Governance With Gr...
31mEverything You Need to Know About Prometheus 3.0
06mLightning Talk: Prometheus Bug Scrub
18mMaking Prometheus even more open
27mWelcome + Project Updates
54mPrometheus – what’s new and what’s next?
25mPrometheus Data analysis and Event Notifications for Progressive Delivery
04mLightning Talk: Prometheus Rules management and validation