release and distribution

[albx79]

I have reserved a name on the official Rust package repository (https://crates.io/crates/what-bump). At the moment it contains a hello world, but once we go open, I can publish the actual code there (manually, from my PC).

However, we have two desiderata:

1. One shouldn't need my PC to do a release; it should be an automated workflow managed by CicleCI
2. cargo install shouldn't be the only way to get what-bump; ideally there should be a homebrew formula for people who don't have the rust toolchain installed
   • other package managers are acceptable too, but we believe that homebrew is best suited for CLI apps
   • I'm open to hearing options, especially for Linux where homebrew is not that widespread

[albx79]

Getting project version from the command line using cargo and jq:
cargo metadata --no-deps | jq ".packages[0].version"

Listing release tag with newest on top (and "head" to get latest version):
git tag | grep -E '[0-9]+.[0-9]+.[0-9]+.*' | sort -rV | head -1

[albx79]

The release process should perform the following steps:

• bump version
• tag git
• build release artifact that's available to download from github
• build docker image that's available on dockerhub
• publish to crates.io
• generate the change log, that's available as release notes on github

Also, it should be:

• performed entirely on CI
• manually triggered by merging onto a special branch

For this to work properly, it's mandatory that we address #16 (handle multi-parent commits), so that version bump and change log generation can be performed across multiple branches.

[albx79]

The latest release script does pretty much everything there is to do (version bump, tag, create release, build docker image, upload artifact to github, upload image to docker hub, and upload sources to crates.io).

The next step is to run the whole script inside a container, so that it will be eventually possible to run it on circleci.