Skip to content

Instantly share code, notes, and snippets.

@groundwater

groundwater/BIGVER.md

Created September 23, 2014 16:09
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save groundwater/22408b1eb9bfe77adee3 to your computer and use it in GitHub Desktop.
Save groundwater/22408b1eb9bfe77adee3 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
BIGVER.md

BIGVER

The BIGVER spec is a semver.io compatible versioning scheme

Rules

  1. all new versions must increment the major version always
@retrohacker
Copy link

I like this, however I believe we could increase the information conveyed by the version if we partitioned use cases for the minor and patch versions.

  1. all new versions must increment the major version always. They must be deployed without any unit tests or documentation. #.0.0
  2. Immediately following the major version bump, we reintegrate our unit tests and deploy as #.#.0
  3. Finally, we integrate our documentation (readmes, .chm files, and clippy extensions). This is deployed as #.#.#

Any updates to unit tests and readme's require a full major version bump followed by the above steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment