Meta/MaintNotes: adjust to 2.8/2.7.4
Junio C Hamano committed
Mar 28, 2016 at 13:44 UTC
7d94dc147a0fd9f23e635716e47b74a342787875
1 file changed
+4
-3
MaintNotes
+4
-3
@@ -1,3 +1,4 @@
1
+To: git@vger.kernel.org
2
Subject: A note from the maintainer
3
4
Welcome to the Git development community.
@@ -134,7 +135,7 @@ named with three dotted decimal digits (e.g. "1.8.5"), but recently we
135
switched the versioning scheme and "feature releases" are named with
136
three-dotted decimal digits that ends with ".0" (e.g. "1.9.0").
137
137
-The last such release was 2.7.0 done on Jan 4th, 2016. You can expect
138
+The last such release was 2.8.0 done on Mar 28th, 2016. You can expect
139
that the tip of the "master" branch is always more stable than any of
140
the released versions.
141
@@ -145,8 +146,8 @@ are cut from it. The maintenance releases used to be named with four
146
dotted decimal, named after the feature release they are updates to
147
(e.g. "1.8.5.1" was the first maintenance release for "1.8.5" feature
148
release). These days, maintenance releases are named by incrementing
148
-the last digit of three-dotted decimal name (e.g. "2.6.3" is the
149
-third maintenance release for the "2.6" series).
149
+the last digit of three-dotted decimal name (e.g. "2.7.4" is the
150
+fourth maintenance release for the "2.7" series).
151
152
New features never go to the 'maint' branch. This branch is also
153
merged into "master" to propagate the fixes forward as needed.