automate releases

[igalic]

The last release, 0.5.0 we made did not bump the version number.

We should automate our releases as far as possible.
In an ideal world, anyone could trigger a release by proposing a PR that includes a Changelog and bumps some version numbers.

Right now, we don't have a Changelog in the repo itself.
But there are 7(!!!) places (Cargo.toml files) where a version needs to be bumped.

How to mitigate this?

we could have a pre-release helper… script, or cargo target??, that helps with the PR: it bumps all the versions, and creates a Changelog.md entry. That changelog.md entry can either be a template that needs to be filled out by the person proposing the release-pr, or it could be generated from github.

Once that PR is merged, we'd run another helper script that tags the version, and creates a Github release from the Changelog entry. Perhaps some time in the future, we could also push a release out to https://crates.io/crates/plume if we can convince @bochecha to… trade places… ooooooooooor, we could just call our crate plume-blog ?

The script should also bump the versions to x.y.z-dev (or x.y.z-githash), so we know when somebody is running an unreleased version.

[igalic]

Aparently, cargo-release can help us with most of these!

[igalic]

started a patch here: #790