MaintNotes: updte for 2.40
Junio C Hamano committed
Mar 13, 2023 at 09:50 UTC
c49b011830b1c101662dad9a55e5b4c03ac9739c
1 file changed
+7
-3
MaintNotes
+7
-3
@@ -179,7 +179,7 @@ named with three dotted decimal digits (e.g. "1.8.5"), but we have
179
switched the versioning scheme and "feature releases" are named with
180
three-dotted decimal digits that ends with ".0" (e.g. "1.9.0").
181
182
-The last such release was 2.38 done on Oct 3rd, 2022. You can expect
182
+The last such release was 2.40 done on Mar 13rd, 2023. You can expect
183
that the tip of the "master" branch is always more stable than any of
184
the released versions.
185
@@ -224,7 +224,10 @@ and all topics that are remotely promising from the list traffic, so
224
please do not read too much into a topic being on (or not on) the "seen"
225
branch. This branch is mainly to remind the maintainer that the topics
226
in them may turn out to be interesting when they are polished, nothing
227
-more. The topics on this branch aren't usually complete, well tested,
227
+more, but can be used by contributors to anticipate what topics from
228
+others may cause conflict with your work, and find people who are working.
229
+on these topics to talk to before the potential conflicts get out of
230
+control. The topics on this branch aren't usually complete, well tested,
231
or well documented and they often need further work. When a topic that
232
was in "seen" proves to be in a testable shape, it is merged to "next".
233
@@ -234,7 +237,8 @@ to be not so good and the topic can be dropped from "seen" in such a case.
237
The output of the above "git log" talks about a "jch" branch, which is an
238
early part of the "seen" branch; that branch contains all topics that
239
are in "next" and a bit more (but not all of "seen") and is used by the
237
-maintainer for his daily work.
240
+maintainer for his daily work. Using the tip of this branch, instead of
241
+'next', as your daily driver is also recommended.
242
243
The two branches "master" and "maint" are never rewound, and "next"
244
usually will not be either. After a feature release is made from