Post 1.6.4 MaintNotes updates
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Jul 29, 2009 at 13:34 UTC
ae4fdb1d2a8d45bb5b9d990f9ad57a3b4750bc6e
1 file changed
+3
-3
MaintNotes
+3
-3
@@ -80,7 +80,7 @@ automate a task.
80
81
There are four branches in git.git repository that track the
82
source tree of git: "master", "maint", "next", and "pu". I may
83
-add more maintenance branches (e.g. "maint-1.5.4") if we have
83
+add more maintenance branches (e.g. "maint-1.6.3") if we have
84
hugely backward incompatible feature updates in the future to keep
85
an older release alive; I may not, but the distributed nature of
86
git means any volunteer can run a stable-tree like that herself.
@@ -92,7 +92,7 @@ but they are not expected to be anything major, and more
92
importantly quickly and trivially fixable. Every now and
93
then, a "feature release" is cut from the tip of this branch and
94
they typically are named with three dotted decimal digits. The
95
-last such release was 1.6.3 done on May 6th 2009. You
95
+last such release was 1.6.4 done on Jul 29th 2009. You
96
can expect that the tip of the "master" branch is always more
97
stable than any of the released versions.
98
@@ -101,7 +101,7 @@ from "master" at that point. Obvious, safe and urgent fixes
101
after a feature release are applied to this branch and
102
maintenance releases are cut from it. The maintenance releases
103
are named with four dotted decimal, named after the feature
104
-release they are updates to; the last such release was 1.6.2.5.
104
+release they are updates to; the last such release was 1.6.3.4.
105
New features never go to this branch. This branch is also
106
merged into "master" to propagate the fixes forward.
107