Release plan proposal

[ctron]

Here's an idea for creating releases.

We should create releases often, but not too often. We also should indicate our confidence in a release.

All of this has been solved with SemVer, so let's use it.

My proposal is that we create a pre-release every week. More specifically, every Thursday around 12:00 UTC (aka twelve hundred hrs). Coincidentally, that's lunch time, and builds can run just fine during that time. It also is the day we have meetings where we could demo exactly that release.

Those weekly releases start with -alpha.1 until we vote to move to -beta.1, then to -rc.1. And then to a proper release.

The next release is a new minor (0.2.0) release. We stick with 0.x.0 for as long as we like.

For now, we don't create release branches.

I'll write up a RELEASE.md document. We will take turns performing the release. The actual process should be pretty automated by now.

This is purely upstream. If QE wants to test those released artifacts, we can of course get them on board somehow. I would prefer this, but it's optional.

[ctron]

Let's try to live it then.