Skip to content

Latest commit

 

History

History
33 lines (20 loc) · 1.01 KB

RELEASING.rst

File metadata and controls

33 lines (20 loc) · 1.01 KB

Releasing execnet

This document describes the steps to make a new execnet release.

Version

master should always be green and a potential release candidate. execnet follows semantic versioning, so given that the current version is X.Y.Z, to find the next version number one needs to look at the CHANGELOG.rst file:

  • If there any new feature, then we must make a new minor release: next release will be X.Y+1.0.
  • Otherwise it is just a bug fix release: X.Y.Z+1.

Steps

To publish a new release X.Y.Z, the steps are as follows:

  1. Create a new branch named release-X.Y.Z from the latest master.
  2. Update the CHANGELOG.rst file with the new release information.
  3. Commit and push the branch to upstream and open a PR.
  4. Once the PR is green and approved, start the deploy workflow manually from the branch release-VERSION, passing VERSION as parameter.
  5. Merge the release PR to master.