RELEASING.md

Releasing Estella

There're no hard rules about when to release estella. Release bug fixes frequenty, features not so frequently and breaking API changes rarely.

Release

Run tests, check that all tests succeed locally.

bundle install
rake

Check that the last build succeeded in Circle CI for all supported platforms.

Increment the version, modify lib/estella/version.rb.

• Increment the third number if the release has bug fixes and/or very minor features, only (eg. change 0.2.1 to 0.2.2).
• Increment the second number if the release contains major features or breaking API changes (eg. change 0.2.1 to 0.3.0).

Change "Next Release" in CHANGELOG.md to the new version.

### 0.2.2 (1/17/2017)

Remove the line with "Your contribution here.", since there will be no more contributions to this release.

Commit your changes.

git add README.md CHANGELOG.md lib/estella/version.rb
git commit -m "Preparing for release, 0.2.2."
git push origin main

Release.

$ rake release

estella 0.2.2 built to pkg/estella-0.2.2.gem.
Tagged v0.2.2.
Pushed git commits and tags.
Pushed estella 0.2.2 to rubygems.org.

Prepare for the Next Version

Increment the third version number in lib/estella/version.rb.

Add the next release to CHANGELOG.md.

### 0.2.3 (Next)

* Your contribution here.

Comit your changes.

git add CHANGELOG.md lib/estella/version.rb
git commit -m "Preparing for next development iteration, 0.2.3."
git push origin main