56bbdc73f4 · matheusbsbs/matheus-bagliano

@@ -42,12 +42,12 @@ project convention.

42

43 If you sent a patch and you did not hear any response from anybody for

44 several days, it does not necessarily mean that your patch was totally

45 -uninteresting; it may merely mean that it was lost in the noise. Please

46 -do not hesitate to send a reminder message in such a case. Messages

47 -getting lost in the noise may be a sign that those who can evaluate

48 -your patch don't have enough mental/time bandwidth to process them

49 -right at the moment, and it often helps to wait until the list traffic

50 -becomes calmer before sending such a reminder.

45 +uninteresting; it may merely mean that it was lost in the noise.

46 +Please do not hesitate to send a reminder message in such a case.

47 +Messages getting lost in the noise may be a sign that those who can

48 +evaluate your patch don't have enough mental/time bandwidth to process

49 +them right at the moment, and it often helps to wait until the list

50 +traffic becomes calmer before sending such a reminder.

51

52 The list archive is available at a few public sites:

53

@@ -70,7 +70,7 @@ so, like this:

70

71 Often these web interfaces accept the message ID with enclosing <>

72 stripped (like the above example to point at one of the most important

73 -message in the Git list).

73 +message in the Git mailing list).

74

75 Some members of the development community can sometimes be found on

76 the #git and #git-devel IRC channels on Libera Chat. Their logs are

@@ -162,7 +162,7 @@ found in:

162 https://repo.or.cz/git-{htmldocs,manpages}.git/

163 https://github.com/gitster/git-{htmldocs,manpages}.git/

164

165 -The manual pages formatted in HTML for the tip of 'master' can be

165 +The manual pages formatted in HTML for the tip of "master" can be

166 viewed online at:

167

168 https://git.github.io/htmldocs/git.html

@@ -183,11 +183,12 @@ ready to be used in a production setting. Every now and then, a

183 "feature release" is cut from the tip of this branch. They used to be

184 named with three dotted decimal digits (e.g., "1.8.5"), but we have

185 switched the versioning scheme and "feature releases" are named with

186 -three-dotted decimal digits that ends with ".0" (e.g., "1.9.0").

186 +ttwo-dotted decimal digits (e.g. "2.53"), whose tag ends with ".0"

187 +(e.g., "v2.53.0").

188

188 -The last such release was 2.52 done on Nov 17th, 2025. We aim to keep

189 -that the tip of the "master" branch is always more stable than any of

190 -the released versions.

189 +The last such release was Git 2.53, made on Feb 2nd, 2026. We aim to

190 +make sure that the tip of the "master" branch is always more stable

191 +than any of the released versions.

192

193 Whenever a feature release is made, "maint" branch is forked off from

194 "master" at that point. Obvious and safe fixes for bugs in the latest

@@ -225,7 +226,10 @@ without major breakage. A topic that is in "next" is expected to be

226 polished to perfection before it is merged to "master". Please help

227 this process by building & using the "next" branch for your daily

228 work, and reporting any new bugs you find to the mailing list, before

228 -the breakage is merged down to the "master".

229 +the breakage is merged down to the "master". This process depends on

230 +your participation, as the way you use Git may be unique from others,

231 +and a new bug may only manifest itself when used in the way you use

232 +Git, not noticed by others.

233

234 The "seen" branch bundles the remaining topic branches that the

235 maintainer happens to have seen to remind the maintainer that the

@@ -241,12 +245,13 @@ by others may cause conflicts with their own work, and find people who

245 are working on these topics to talk to before the potential conflicts

246 get out of control. It would be a good idea to fork your work from

247 maint or master and to (1) test it by itself, (2) test a temporary

244 -merge of it to 'next' and (3) test a temporary merge to it to 'seen',

245 -before publishing it.

248 +merge of it to "next" and (3) test a temporary merge to it to "seen",

249 +before sending it to the list (or asking GitGitGadget to send it to

250 +the list).

251

247 -You can run "git log --first-parent master..seen" to see what topics

248 -are currently in flight. The output of the above "git log" talks

249 -about a "jch" branch, which is an early part of the "seen" branch;

252 +You can run "git log --oneline --first-parent master..seen" to see

253 +what topics are currently in flight. The output of the above command

254 +talks about a "jch" branch, which is an early part of the "seen" branch;

255 that branch contains all topics that are in "next" and a bit more (but

256 not all of "seen") and is used by the maintainer for his daily work.

257

@@ -273,7 +278,14 @@ Note that being in "next" is not a guarantee to appear in the next

278 release, nor even in any future release. There were cases that topics

279 needed reverting a few commits in them before graduating to "master",

280 or a topic that already was in "next" was reverted from "next" because

276 -fatal flaws were found in it after it was merged to "next".

281 +fatal flaws were found in it after it was merged to "next". The same

282 +can be said to "master"---there were cases that we needed to revert a

283 +topic from it because a regression was found after it was merged to

284 +"master", instead of while it was still in "next". To prevent it from

285 +happening, those who care about the quality of the next release, those

286 +who want to ensure that the next release will not break their

287 +workflow, are strongly encouraged to build and try out "next" in their

288 +daily work and report problems.

289

290

291 * Other people's trees.

MaintNotes - update post 2.53