The spec is released each calendar quarter. The target release dates are within the
following ranges:
* Q1: January 20-27 (critically, before FOSDEM).
* Q2: May 20-27.
* Q3: August 20-27.
* Q1: January 20-27 (if needed before FOSDEM) or February 21-28.
* Q2: May 15-22.
* Q3: August 1-7 or August 20-27 depending on feature requirements.
* Q4: November 1-15 (before recurring November conflicts, like IETF).
The SCT aims to have dates picked out by:
* Q1: January 10.
* Q2: May 1.
* Q3: August 1.
* Q4: October 15.
The SCT aims to have dates picked out 2 weeks before the chosen release date. When
possible, releases should be scheduled for Thursdays and Fridays to allow a few
consecutive business days for identifying blockers.
When a release date is picked, a [checklist](https://github.com/matrix-org/matrix-spec/issues/new?assignees=&labels=release-blocker&projects=&template=release.md&title=Matrix+1.X)
issue is created to track details of the release. Release blockers should continue to
be accepted up until 7 calendar days prior to the release date.
issue is created to track details of the release. Release blockers should continue
to be accepted at the discretion of whoever is doing the release (typically, blockers
should be allowed up to 1-2 days before the release date).
**Release dates are not promises.** The SCT reserves the ability to change, cancel,
postpone, etc a release for any reason. Do not rely on a release happening on a given
day until the release has actually happened & blog post published.
Once a release is scheduled, the SCT will begin planning what the next release is
Once a release is *scheduled*, the SCT will begin planning what the next release is
expected to look like. The plan should be included in the spec release blog post,
and be ready for execution on spec release day. Plans are guides and not promises.
A blog post for the SCT members to review should be ready at minimum 1 week before
the target release date. 1-2 days before the release itself, the prerequisite steps
below are executed to ensure the spec release can go ahead.
A blog post for the SCT members to review should be ready 2-3 days prior to the
release at minimum. Preferably a week in advance.
1-2 days before the release itself, the prerequisite steps below are executed to
ensure the spec release can go ahead.
## Release composition
*This section is a work in progress.*
Mentioned above, the SCT aims to have spec releases quarterly. Each quarter has a
slightly different theme to it:
Spec releases do not currently have attached themes, though when planning a release
a broad theme may be considered. Ideally, each release contains a "hero feature"
which is highlighted in the later blog post.
* Q1: Massive feature release, if possible. This generally happens thanks to FOSDEM.
* Q2: Regular feature release, if possible.
* Q3: Momentum-continuing feature release, if possible.
* Q4: Preferably a maintenance release, but will accept features per normal.
Maintenance-only releases are discouraged, but typical in Q4 to give implementations
a small bit of reprieve from feature development.
## Prerequisites / preparation
@ -115,12 +114,16 @@ release.
## Patching a release
From time to time we'll need to update a release in the wild. Examples include fixing typos,
updating build machinery, etc. Typically it is not considered a good idea to patch a release
more than 1 month after the original release date - this is because the administrative effort
is typically best reserved for the next release cycle.
Patch releases are used to fix the most recent release on record. Typically a patch
release will be deployed if there is an issue with the build machinery, a factual
error is introduced by the release, or there are notable clarity issues introduced
by the release which may affect implementation. In all cases, patch releases should
*not* be used if more than 2-4 weeks have passed since the release.
Typos and similar do not generally require a patch release.
**Patch releases are not to be used for spec changes. Only typos and equivalent.**
**Patch releases must not to be used for spec changes (new MSCs, etc) beyond fixing
factual errors.**
1. Add the required changes to the release branch (`release/v1.2` for example).
2. Fast forward the `v1.2` tag to the release branch head.
Travis Ralston
2 months ago
committed by