git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Nicolas MAFFRE <nicolas.maffre.external@airbus.com>
Cc: git@vger.kernel.org
Subject: Re: Git v2.20.1 EOS date
Date: Tue, 02 Aug 2022 11:26:52 +0200	[thread overview]
Message-ID: <220802.8635efgf8d.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CAHWqpUPVAvw5bsvS1DgAQDwxhzYmh6_V=r+TfPxekdy-oMZWmg@mail.gmail.com>


On Tue, Aug 02 2022, Nicolas MAFFRE wrote:

> Hello,
>
> I'm working on a project that uses Git v2.20.1 and I need to know
> if there is an "End of support" date for this version of the software Git ?

Yes and no, for v2.20.* it was probably sometime around 2 years ago (see
below).

The Git project doesn't really do LTS or active support for anything
except the current or recent release(s), if there are issues discovered
in older releases they're fixed in newer ones, not in older "maintenance
tracks".

For bugs discovered in older releases they'll almost always only be
fixed in the code that'll become the next release.

For security fixes we do change some older releases, but usually only
the ones from the last 1-2 years. E.g. there was a security release
recently which included point-releases for versions as old as 2.30.*:
https://lore.kernel.org/git/xmqqv8s2fefi.fsf@gitster.g/; So that "2
years" above is just an inference of mine, judging from the last
security release.

How long that Window is is up to Junio's discretion, you can find some
others past such releases at:
https://lore.kernel.org/git/?q=s%3AANNOUNCE+s%3A%22and+others%22+f%3Agitster%40pobox.com

Note that this only goes for the git project. If you're e.g. using some
well-known vendors of LTS software they may themselves commit to
backporting patches to git and other software within their LTS window
(with mixed results).

I hope that helps!

  reply	other threads:[~2022-08-02  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  8:34 Git v2.20.1 EOS date Nicolas MAFFRE
2022-08-02  9:26 ` Ævar Arnfjörð Bjarmason [this message]
2022-08-02 16:12 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=220802.8635efgf8d.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nicolas.maffre.external@airbus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).