Development Process

Starting a ticket

1. Create a new branch from develop with the name of the branch following the convention #<issue-number><lower-case-snaked-name>.
2. Do the work and submit a pull request to the develop branch.

Creating a release candidate

1. Ensure the VERSION file in develop represents the next version which is in development. Corcel follows semantic versioning and a release will either be a MAJOR release, a MINOR release or a PATCH release. Each type may have many builds and this will be reflected in the version number before an actual release is complete.
2. develop is merged into the release branch via a pull request.
3. Any further changes which are required for the release are done via branches off of release and pull requests back into release. Each build of the release branch will create a deployment with an incrementing sequential release candidate number.

Create a release

1. release is merged into master via a pull request
2. Each build of master will create a deployment for that version
3. Any patches required to released versions can be branched from master and merged back via a pull request. They can also follow the entire promotion process depending on when the bug is caught and what has already been merged into develop.