Initial release process

[Aaron Leopold]

While I’m still aiming for a 0.1.0 as the first Stump release, I’d like to kick off the versioning and release process

I feel that Stump has reached a point where it needs to provide a means of rolling back in the event the latest nightly build is poop and causes some breakage. At least aiming for sometime in the next few months.

Versions and changelogs

I'll stick to patch bumps until I feel things are stable enough to make that first minor bump to 0.1.0.

The (future) mobile and (future) desktop apps make versioning and generating changelogs a little awkward, since they largely can have separate release cycles. Every other package/crate/subapp can, for the most part, be lumped together as the “primary” release.

I should be able to nicely start using gitmoji-changelog for the changelogs, but it will break once I start developing and versioning the aforementioned apps. Since there is PLENTY of time to tackle that, I’m pushing that concern aside.

Workflow

What I expect to implement is something along the lines of:

• Create and push a new tag manually when I feel a release is ready
  • Script for generating changelog, bumping the versions throughout the project, and creating/pushing a tag
• CI will build the server image and push it to the registry with the tag

That’s it. With the nightly CI already in place, I'm sure it would be mostly trivial to tweak it to support actual tags.