have a proper release procedure #333
Description
Up to now I've been kind of going "ok I've done some stuff let's put out a release" but for 1 thing:
- heh the current release is broken lawl
- for another we have CI which should be able to do outputs
I'm basically thinking pick out issues to go in release x, label them as such, finish them all, check CI is ok, download a copy from CI and put that as the release.
There should also be integration tests to confirm the GUI doesn't blow up.