From: Junio C Hamano gits...@pobox.com
Philip Oakley philipoak...@iee.org writes:
If we are progressing from V1.9 to V2.0 quickly (one cycle?), which I
understand is the plan, then mixing the minor development items
(patch
series which progress to master) with the maintenance fixes over the
From: Junio C Hamano gits...@pobox.com
Sent: Friday, January 31, 2014 11:14 PM
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
Philip Oakley philipoak...@iee.org writes:
If we are progressing from V1.9 to V2.0 quickly (one cycle?), which I
understand is the plan, then mixing the minor development items (patch
series which progress to master) with the maintenance fixes over the
next few months, thus only having 1.9.x
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
4 matches
Mail list logo
