Skip to content

RELEASE.md

Latest commit

 

History

History
28 lines (18 loc) · 1.86 KB

RELEASE.md

File metadata and controls

28 lines (18 loc) · 1.86 KB

Release Process

Overview

At any given time there are three revisions of the Alertmanager charm available on CharmHub.io, for each of the following channels:

  1. latest/stable is a well tested production ready version of the Charm.
  2. latest/candidate is a feature ready next version of the stable release, currently in testing.
  3. latest/edge is the bleeding edge developer version of the charm. While we really try not to, it may break and introduce regressions.

Currently, the Alertmanager charm does not make use of the latest/beta channel. For more information about CharmHub channels, refer to the Juju charm store documentation.

When to create which revisions

  • Stable revisions are done in consultation with product manager and engineering manager when the candidate revision has been well tested and is deemed ready for production.
  • Candidate revisions are done when the charm reaches a state of feature completion with respect to the next planned stable release.
  • Edge revisions are released at the developer's discretion, potentially every time something is merged into main and the unit tests pass.

How to publish revisions

Refer to the Publish your operator in Charmhub documentation. After a latest/stable release, it is expected that the version of the charm is the same as the one in latest/candidate, and those two channels will diverge again when we are ramping up through latest/candidate releases for a new latest/stable release.

A note on granularity of revisions

We believe in shipping often and with confidence. It is perfectly acceptable to have a new latest/stable release containing just one bug fix or a small new feature with respect to the last one.