You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLOCKWORK_RELEASE_MODEL.md
+26-14Lines changed: 26 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ This document does *not* cover the distribution or publication of artifacts buil
34
34
35
35
Plans for a new release model began in March 2023 and several models were discussed, with this being the final version agreed upon by the organisation's administrative group and approved by the core contributors.
36
36
37
+
An update to the release model was made in February 2025 to accommodate a more frequent Minecraft release schedule and to help limit update sizes further.
38
+
37
39
### Motivations
38
40
39
41
The release cycle for the `2.7.0` version was significant in that it took an unusually long time and included an unusually-large number of additions and changes.
@@ -59,6 +61,11 @@ Members of the organisation and the wider community identified several problems
59
61
60
62
Of these, the principle complaint is that the `2.7.0` version took a significant amount of time to finish and this had an adverse effect on the community and the wider ecosystem.
61
63
64
+
As of February 2025, Mojang has committed to 'drops', which means significant upstream changes happen much more frequently.
65
+
This corresponds to Skript having a much higher lag time on releasing support for new content due to the mismatch in release dates.
66
+
In addition, an uptick in contributions has led to `2.10` being one of the largest updates yet.
67
+
The size of the update meant that some of the previous concerns, like short notice additions and an extensive changelog, were still persistent despite the new release schedule.
68
+
62
69
### Goals
63
70
64
71
Our release model has been designed to achieve the following goals:
@@ -98,6 +105,7 @@ A 'patch' version (labelled `0.0.X`) may contain:
98
105
- Bug fixes
99
106
- Non-impactful<sup>2</sup> improvements to existing features
100
107
- Changes to meta content (e.g. documentation)
108
+
- Opt-in experiments
101
109
102
110
There may be **very rare** occasions when a breaking change is necessary in a patch release. These may occur if and only if: either a breaking change is required in order to fix an issue, and the issue is significant enough to need fixing in a patch rather than waiting for a major release, or an issue occurred with an inclusion in the version immediately-prior to this, which must be changed or reverted in some way.
103
111
@@ -138,18 +146,20 @@ A table of (expected) dates is displayed below.
138
146
| 15th Jan | Feature release | 0.1.0 |
139
147
| 1st Feb | Patch | 0.1.1 |
140
148
| 1st Mar | Patch | 0.1.2 |
141
-
| 1st Apr | Patch | 0.1.3 |
142
-
| 1st May | Patch | 0.1.4 |
143
-
| 1st Jun | Patch | 0.1.5 |
144
-
| 1st Jul | Pre-release | 0.2.0-pre1 |
145
-
| 15th Jul | Feature release | 0.2.0 |
146
-
| 1st Aug | Patch | 0.2.1 |
147
-
| 1st Sep | Patch | 0.2.2 |
148
-
| 1st Oct | Patch | 0.2.3 |
149
-
| 1st Nov | Patch | 0.2.4 |
150
-
| 1st Dec | Patch | 0.2.5 |
151
-
152
-
An estimated 14 releases are expected per year, with 10 patches, 2 pre-releases and 2 feature-releases that immediately follow them.
149
+
| 1st Apr | Pre-release | 0.2.0-pre1 |
150
+
| 15th Apr | Feature release | 0.2.0 |
151
+
| 1st May | Patch | 0.2.1 |
152
+
| 1st Jun | Patch | 0.2.2 |
153
+
| 1st Jul | Pre-release | 0.3.0-pre1 |
154
+
| 15th Jul | Feature release | 0.3.0 |
155
+
| 1st Aug | Patch | 0.3.1 |
156
+
| 1st Sep | Patch | 0.3.2 |
157
+
| 1st Oct | Pre-release | 0.4.0-pre1 |
158
+
| 15th Oct | Feature release | 0.4.0 |
159
+
| 1st Nov | Patch | 0.4.1 |
160
+
| 1st Dec | Patch | 0.4.2 |
161
+
162
+
An estimated 16 releases are expected per year, with 8 patches, 4 pre-releases and 4 feature-releases.
153
163
154
164
Please note that the actual number may differ from this in cases such as:
155
165
- A version requiring multiple pre-releases to correct mistakes (`0.3.0-pre1`, `0.3.0-pre2`)
@@ -160,15 +170,17 @@ There is no fixed timetable for the circulation of unpublished builds to the pub
160
170
161
171
### Major Version Schedule
162
172
163
-
A [feature version](#feature-releases) will be released on the **15th of January** and the **15th of July**.
173
+
A [feature version](#feature-releases) will be released on the **15th of January**, the **15th of April**, the **15th of July**, and the **15th of October**.
164
174
165
-
This will include all finished content from the previous 6 months that was tested in the pre-release.
175
+
This will include all finished content that was tested in the pre-release.
166
176
167
177
Any features, additions or changes that were *not* ready or approved at the time of the pre-release may **not** be included in the feature release [according to goal 3](#goals). \
168
178
The feature release must **not** be delayed to accomodate content that was not ready by the deadline [according to goal 5](#goals).
169
179
170
180
If there is no content ready at the scheduled date of a feature release, the release will be skipped and a notice published explaining this.
171
181
182
+
The April and October releases are intended to include minimal breaking changes and focus more on including new features and opt-in experiments.
183
+
172
184
### Pre-Release Schedule
173
185
174
186
A [pre-release](#pre-releases) will be released on the **1st of January** and the **1st of July**, leaving two weeks before the following release for public testing to occur.
0 commit comments