... | ... | @@ -19,7 +19,7 @@ Major releases are currently produced twice a year. The schedule for a major rel |
|
|
* **Release candidate** is a release is supposed to be ready to go. Sometimes there is a quick succession of release candidates as minor glitches are fixed called `RC1`, `RC2`, etc.
|
|
|
* **Final release**.
|
|
|
|
|
|
We generally strive to have core libraries (`base`) stabilized by alpha 2 or 3.
|
|
|
We generally strive to have breaking changes in core libraries (`base`) in for alpha 1, with non-breaking changes being in by alpha 2 or 3. Similarly, boot library versions (e.g. `text`) should be finalized by alpha 3.
|
|
|
|
|
|
Minor releases generally occur on an as-needed basis without a pre-determined schedule. But once we have decided to make a minor release, we post the schedule on the milestone. Unlike major releases, minor releases do not have an associated set of pre-releases.
|
|
|
|
... | ... | |