We expect a few patch releases providing bugfixes to the 3.x branch whilst MS4 development is ongoing.
There is no intention to create a 3.6 release. New features must be developed against MS4
* UX improvements
* modularisation of code
Basically, normal improvements are expected to
import/export modules. All other modules are subject to architectural refactoring.
From nightly to release
Patch releases are usually jump straight from nightly to final release. Minor and major releases follow the stadia listed below:
Automatic builds per commit/PR. Anything goes and anything may break (but shouldn't of course ;-) )
Tech-preview release. Stability is not guaranteed. Allows testing of new features by a broader audience.
A minor release may have an alpha release if it packs big new features.
A major release can have multiple alpha releases to tease ongoing development progress
Test release. Should be fairly stable. At this point some "must have/fix" issues have been identified and most should be included in this release.
From now on, only bugfixes and low-risk features will be eligible for inclusion. Bugfixes that don't address a "must fix" issue should also be quite low-risk; otherwise they will be pushed out to the next (patch) release
Meant for broad testing.
Only required if changes have been made since Beta. Expected to be stable. At this point only critical bugfixes are still allowed
RC + eventual critical bugfixes