Difference between revisions of "Release schedule"
Jump to navigation
Jump to search
(reformatted, link to past releases) |
|||
| Line 3: | Line 3: | ||
Thus, the nearest future release dates are: | Thus, the nearest future release dates are: | ||
| − | * | + | * 7 Dec 2015 |
| − | * | + | * 7 Mar 2016 |
| + | * 6 Jun 2016 | ||
| + | * 5 Sep 2016 | ||
| + | * 5 Dec 2016 | ||
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 13:47, 12 November 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 future release dates are:
- 7 Dec 2015
- 7 Mar 2016
- 6 Jun 2016
- 5 Sep 2016
- 5 Dec 2016
Approximately 2 weeks before the release the repository is turned into feature-freeze state, when only fixes are accepted.
See also
- Download/criu for past releases