Draft versioning spec for discussion

[jaustin]

We need to balance a number of different factors when deploying the online python editor for the micro:bit Foundation and this is a first draft at outlining what they are and how we could provide users with stability while allowing development to be tested.

This is a PR so we can use GitHub's features to discuss the spec and the deployment @carlosperate @ntoll @whaleygeek

[carlosperate]

I think we are making the Release cadence more complex than it needs to be just for the sake of "keeping order and managing change", when in reality there will be little to manage. I do think it's a good idea to have a "july" changeover, but I think should only be reflected in the version displayed when accessing http://python.microbit.org . If we just keep semantic versioning for stable versions, and a "beta channel" (something like python.microbit.org/beta) for unstable I don't see why we need any more process. When a beta feature is stable it goes into a new version, which can be accessed through a versioned URL, while the default http://python.microbit.org is anchored to a specific version through the year.

[ntoll]

Ping @jaustin. I'm anxious to get the blocks work out ASAP. The sooner this happens the sooner we get feedback and can make quick improvements.

Any response to the feedback above? What are the next steps?

[jaustin]

@microbit-matt - tagging you here as it's probably time to pick this up again :)