[Release Process] Overview

Introduction

This is intended to document the steps involved in doing a release of Bolt.

1. Merge open PRs for release/X.Y, or re-target their merge base
2. Declaring release/X.Y End of Life,i.e. all PRs to release/X.Z
3. Merging branches

• X.Y -> X.Z -> master

1. Setting release/X.Z to be default branch
2. Branch release/X.Z + 1

• Update branch aliases for both release/X.Z + 1 and master
• Push new branches
• Update:
  • dev.bolt.cm/repository
  • dev.bolt.cm/sami/sami-config-bolt-api.php
  • dev.bolt.cm/sami/sami-config-bolt-api-internal.php

1. Tag X.Z.0
2. Release
3. Update roadmap (on major or minor releases)

Assumptions

Tracker

A GitHub issue used to list and record open, closed, and moved issues.

Open
-------

- #1000 A koala ate my Clippy
- #1555 History in the making **[Fixed in #1234]**

Closed
---------

- ~~#911 Dude, where's my car?~~ **[Fixed in #2000]**

Moved
---------

- #1 Port Bolt to Go to keep [BoltIssueBall] happy **[Moved to X.Y]**

• Tracker cleared
  • Tracker points marked as "moved", have tracking points added to next appropriate tracker ()

Alpha & Beta

Stable

• Merge development branch to master
• Update $values['bolt_version'] and $values['bolt_name'] in src/Application.php
• Run unit tests
• Execute test schedule
• Tag this change as 'bolt_version'
• Push to GitHub
• Create archives