Skip to content

Latest commit

 

History

History
50 lines (33 loc) · 1.34 KB

MAINTAINING.md

File metadata and controls

50 lines (33 loc) · 1.34 KB
Raw

Drone-GDM: Maintaining

This document provides instructions for drone-gdm maintainers. For general development instructions, see DEVELOPMENT.md.

Releases

Releases are cut using git tags. The tags use a modified subset of semantic versioning, as indicated below.

TL;DR: Releases are in the form M.m.p[a|b], i.e. the semantic major, minor, and patch numbers and - optionally - a prerelease suffix (which must be either a or b).

😬 Semver compliance is on the TODO list.

Cutting a New Release

To cut a new release:

  1. Build and test locally
  2. git push origin main
  3. Verify that the build passed
  4. Verify that the latest docker tag was updated
  5. Update the CHANGELOG with relevant info
  6. git tag -a <version>
  7. git push origin main <version>
  8. Verify that the release docker tag was updated

Tag Format Spec

<valid tag> ::= <version core>
              | <version core><pre-release>

<version core> ::= <major> "." <minor> "." <patch>

<major> ::= <digits>

<minor> ::= <digits>

<patch> ::= <digits>

<digits> ::= <digit>
           | <digit> <digits>

<digit> ::= 0-9

<pre-release> ::= "a" | "b"