Meta/MaintNotes: mention 'git bugreport' and adjust the latest release number
Junio C Hamano committed
Oct 29, 2020 at 15:02 UTC
7b0113f8769f451d916728c48af34a7786a39a35
1 file changed
+5
-4
MaintNotes
+5
-4
@@ -111,7 +111,8 @@ Please remember to always state
111
- how the last two are different.
112
113
See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for further
114
-hints.
114
+hints. Our `git bugreport` tool gives you a handy way you can use to
115
+make sure you do not forget these points when filing a bug report.
116
117
If you think you found a security-sensitive issue and want to disclose
118
it to us without announcing it to wider public, please contact us at
@@ -172,7 +173,7 @@ named with three dotted decimal digits (e.g. "1.8.5"), but we have
173
switched the versioning scheme and "feature releases" are named with
174
three-dotted decimal digits that ends with ".0" (e.g. "1.9.0").
175
175
-The last such release was 2.27 done on Jun 1st, 2020. You can expect
176
+The last such release was 2.29 done on Oct 19th, 2020. You can expect
177
that the tip of the "master" branch is always more stable than any of
178
the released versions.
179
@@ -185,8 +186,8 @@ of last-minute issues. The maintenance releases used to be named with
186
four dotted decimal, named after the feature release they are updates
187
to (e.g. "1.8.5.1" was the first maintenance release for "1.8.5"
188
feature release). These days, maintenance releases are named by
188
-incrementing the last digit of three-dotted decimal name (e.g. "2.26.1"
189
-was the first maintenance release for the "2.26" series).
189
+incrementing the last digit of three-dotted decimal name (e.g. "2.29.2"
190
+was the second maintenance release for the "2.29" series).
191
192
New features never go to the 'maint' branch. It is merged into "master"
193
primarily to propagate the description in the release notes forward.