| commit | c7b8cf49850c59d5583d81a30dd7d1f1d18748bf | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Fri, 31 Jan 2014 23:14:05 +0000 (31 15:14 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 5 Feb 2014 22:14:00 +0000 (5 14:14 -0800) | ||
| tree | 2b72c5211157c296bd8974780defdc23fe1055c4 | treesnapshot (tar.gz zip) |
| parent | 2171c0c36fb1edbacf17c14490cbe935269dcd04 | commitdiff |
howto/maintain-git.txt: new version numbering scheme
We wanted to call the upcoming release "Git 1.9", with its
maintenance track being "Git 1.9.1", "Git 1.9.2", etc., but various
third-party tools are reported to assume that there are at least
three dewey-decimal components in our version number.
Adjust the plan so that vX.Y.0 are feature releases while vX.Y.Z
(Z > 0) are maintenance releases.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We wanted to call the upcoming release "Git 1.9", with its
maintenance track being "Git 1.9.1", "Git 1.9.2", etc., but various
third-party tools are reported to assume that there are at least
three dewey-decimal components in our version number.
Adjust the plan so that vX.Y.0 are feature releases while vX.Y.Z
(Z > 0) are maintenance releases.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/howto/maintain-git.txt | diffblobblamehistory |