|
@@ -66,27 +66,27 @@ curl release scheduling
|
|
|
Release Cycle
|
|
|
-------------
|
|
|
|
|
|
-We do releases every 8 weeks on Wednesdays. If critical problems arise, we can
|
|
|
-insert releases outside of the schedule or we can move the release date - but
|
|
|
-this is rare.
|
|
|
+We normally do releases every 8 weeks on Wednesdays. If important problems
|
|
|
+arise, we can insert releases outside the schedule or we can move the release
|
|
|
+date.
|
|
|
|
|
|
-Each 8 week release cycle is split in two 4-week periods.
|
|
|
+Each 8 week (56 days) release cycle is divided into three distinct periods:
|
|
|
|
|
|
-- During the first 4 weeks after a release, we allow new features and changes
|
|
|
- to curl and libcurl. If we accept any such changes, we bump the minor number
|
|
|
- used for the next release.
|
|
|
+- During the first 10 calendar days after a release, we are in "cool down". We
|
|
|
+ do not merge features but only bug-fixes. If a regression is reported, we
|
|
|
+ might do a follow-up patch release.
|
|
|
|
|
|
-- During the second 4-week period we do not merge any features or changes, we
|
|
|
- then only focus on fixing bugs and polishing things to make a solid coming
|
|
|
- release.
|
|
|
+- During the following 3 weeks (21 days) there is a feature window: we allow
|
|
|
+ new features and changes to curl and libcurl. If we accept any such changes,
|
|
|
+ we bump the minor number used for the next release.
|
|
|
|
|
|
-- After a regular procedure-following release (made on Wednesdays), the
|
|
|
- feature window remains closed until the following Monday in case of special
|
|
|
- actions or patch releases etc.
|
|
|
+- During the next 25 days we are in feature freeze. We do not merge any
|
|
|
+ features or changes, and we only focus on fixing bugs and polishing things
|
|
|
+ to make the pending release a solid one.
|
|
|
|
|
|
If a future release date happens to end up on a "bad date", like in the middle
|
|
|
-of common public holidays or when the lead release manager is away traveling,
|
|
|
-the release date can be moved forwards or backwards a full week. This is then
|
|
|
+of common public holidays or when the lead release manager is unavailable, the
|
|
|
+release date can be moved forwards or backwards a full week. This is then
|
|
|
advertised well in advance.
|
|
|
|
|
|
Critical problems
|
|
@@ -107,7 +107,6 @@ Coming dates
|
|
|
Based on the description above, here are some planned release dates (at the
|
|
|
time of this writing):
|
|
|
|
|
|
-- March 20, 2023 (8.0.0 - curl 25 years)
|
|
|
- May 17, 2023
|
|
|
- July 19, 2023
|
|
|
- September 6, 2023
|
|
@@ -115,3 +114,4 @@ time of this writing):
|
|
|
- December 27, 2023
|
|
|
- February 21, 2024
|
|
|
- April 17, 2024
|
|
|
+- June 12, 2024
|