Difference between revisions of "Release schedule"
Jump to navigation
Jump to search
(rm past releases) |
(1.6 is out) |
||
| Line 1: | Line 1: | ||
Starting from 1.3, CRIU uses the time-driven release model with strict release dates. The rule is simple -- we tag the new version on the 1st Monday of the first month of every season. This timetable is chosen to make releases predictable, not too often and not too rate and not to clash with popular holidays, like New Year and Victory Day in Russia or Christmas and Thanksgiving in the US. Thus, the nearest releases will be: | Starting from 1.3, CRIU uses the time-driven release model with strict release dates. The rule is simple -- we tag the new version on the 1st Monday of the first month of every season. This timetable is chosen to make releases predictable, not too often and not too rate and not to clash with popular holidays, like New Year and Victory Day in Russia or Christmas and Thanksgiving in the US. Thus, the nearest releases will be: | ||
| − | |||
* 1.7 -- 7 Sep 2015 | * 1.7 -- 7 Sep 2015 | ||
* 1.8 -- 7 Dec 2015 | * 1.8 -- 7 Dec 2015 | ||
Approximately 2 weeks before the release the repository is turned into feature-freeze state, when only fixes are accepted. | Approximately 2 weeks before the release the repository is turned into feature-freeze state, when only fixes are accepted. | ||
Revision as of 12:12, 1 June 2015
Starting from 1.3, CRIU uses the time-driven release model with strict release dates. The rule is simple -- we tag the new version on the 1st Monday of the first month of every season. This timetable is chosen to make releases predictable, not too often and not too rate and not to clash with popular holidays, like New Year and Victory Day in Russia or Christmas and Thanksgiving in the US. Thus, the nearest releases will be:
- 1.7 -- 7 Sep 2015
- 1.8 -- 7 Dec 2015
Approximately 2 weeks before the release the repository is turned into feature-freeze state, when only fixes are accepted.