Skip to content
This repository has been archived by the owner on Jul 7, 2020. It is now read-only.

Commit

Permalink
docs: Fix minor inconsistencies in release management
Browse files Browse the repository at this point in the history
  • Loading branch information
@jarrpa
jarrpa authored Aug 24, 2017
1 parent 23dba9d commit 110ac25
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/release-maintenance.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ gluster-kubernetes project.

The project will only support and actively maintain two branches, `master` and
the latest release branch. The latest release branch will always be reachable
by two HEADs, either `<VERSION>-stable` or just `stable`. Requests for support
of older branches may be considered on a case-by-case basis, but users will be
by two HEADs, `<VERSION>-latest` and `stable`. Requests for support of older
branches may be considered on a case-by-case basis, but users will be
encouraged to use newer versions where possible.

## Version Numbering
Expand Down Expand Up @@ -45,9 +45,9 @@ new release is made, the `stable` branch will be moved to follow the new
release branch.

Each MAJOR and MINOR release will get its own branch, forked from `master`.
Each release branch name will be of the form `<version>-latest`, e.g.
Each release branch name will be of the form `<VERSION>-latest`, e.g.
`1.0-latest`. PATCH releases to those versions will be made in those branches,
and will be marked by tags of the form `v<version>`, e.g. `v1.0.0`. PATCH
and will be marked by tags of the form `v<VERSION>`, e.g. `v1.0.0`. PATCH
releases may contain more than one commit, depending on the whimsy of the
release engineers. :)

Expand Down

0 comments on commit 110ac25

Please sign in to comment.