Skip to content

Latest commit

 

History

History
51 lines (34 loc) · 1.07 KB

RELEASING.md

File metadata and controls

51 lines (34 loc) · 1.07 KB
Raw

We follow Semver for our releases.

Branch: master

The master branch should be targeted for PRs that will be included in the next release.

Release Tags

Each release tag follows the format vN.A.X.

N -> major release | A -> minor release | X -> patch release

Example 
	- Major Release
		v1.2.0 -> v2.0.0
	- Minor Release
		v2.0.0 -> v2.1.0
	- Patch Release
		v2.0.0 -> v2.0.1

Release across Gitopia Components

[Gitopia, Gitopia Web, Git Remote Gitopia, Git Server, Gitopia JS]

All Major Release should be compatible with Major Releases of other components regardless of the Minor and Patch releases.

In short, vN of all components should be cross compatible.

Example
	- v1.2.0 of Gitopia should be compatible with v1.0.0
  	of Gitopia Web.
	- v4.0.0 of Gitopia may or may not be compatible with 
  	v1.1.0 of Git Server.

Major Release

  • Include API breaking changes.
  • Introduce new transactions.
  • Remove transactions.

Minor Release

  • Include bug fixes.

Patch Release

  • Include internal refactoring.