Git v2.28.0

Posted Jul 29, 2020 19:56 UTC (Wed) by pizza (subscriber, #46)
In reply to: Git v2.28.0 by jeffcook
Parent article: Git v2.28.0

Um, LWN reports when Mercurial, Fossil, Subversion, or whatever release new versions.

It's hardly LWN's fault that Git's development velocity and release cadence is an order of magnitude (or so) higher than everything else.

Other VCS systems

Posted Jul 29, 2020 20:38 UTC (Wed) by corbet (editor, #1) [Link] (2 responses)

At least, we announce new versions when we actually have a release announcement to work from. Some projects are rather better about sending those out than others.

Other VCS systems

Posted Aug 4, 2020 15:02 UTC (Tue) by gracinet (guest, #89400) [Link] (1 responses)

Hi Jon,

here's evidence that the Mercurial project would be interested: https://www.mercurial-scm.org/pipermail/mercurial/2020-Ju...

What would be the procedure? An announcement on a mailing-list or a link to a blog post, plus a notification on lwn@lwn.net?

I understand it's not a right to get announcements relayed here.

Thank you all for your work.

Other VCS systems

Posted Aug 4, 2020 15:08 UTC (Tue) by corbet (editor, #1) [Link]

Send an announcement to lwn@lwn.net, thanks.

Git v2.28.0

Posted Aug 4, 2020 15:20 UTC (Tue) by gracinet (guest, #89400) [Link]

> [It's hardly LWN's fault that] Git's development velocity and release cadence is an order of magnitude (or so) higher than everything else.

I don't believe this latter statement to be so true.

For instance, Mercurial has a three month release cadence, and I can count 512 non merge commits in the three months between versions 5.3 (last January) and 5.4 (April). Of course, the relevance of a commit count is highly subjective.

Disclaimer: I'm a Mercurial contributor, and I don't believe it's LWN's fault either :-)