Skip to content

Release Strategy

ProgramX-NPledger edited this page Jan 14, 2024 · 2 revisions

Releases are handled within the GitHub workflow/project management functionality.

The order of releases is:

Many Pull Requests --> release/beta (generates a build/release) --> main (generates a build/release)

Pull Requests

Developers are welcome to submit their Pull Requests, which should target the /release/beta branch. The Pull Request, on approval, will merge with pre-production code. This allows those users who are keen to experiment or access new features can do so whilst ensuring the Production build is safe for use.

Beta

The release/beta branch is used to build a pre-release version of Taggloo. Merges into this branch will generate a build, resulting in an approved pre-release build always being available on the branch.

Production

The main branch is considered stable and suitable for Production use. Merges into this branch from release/beta are less frequent, providing a more stable release cadence for comfort and reduction of risk.

Clone this wiki locally