Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: "Bence Csókás" <bence.csokas@arm.com>
To: tools@kernel.org
Subject: [Q] Release calendar archives, EOL calendar?
Date: Mon, 5 Oct 2026 15:08:09 +0200	[thread overview]
Message-ID: <a7c5f068-be55-4df4-a7f2-5a4e44957b3c@arm.com> (raw)

Hi,

not sure if this is the right ML, so do tell me off if not...

I'm a big fan of the Linux releases calendar [1], I've been using it for
close to two years, and have it added to most of my Thunderbird instances.

[1] https://www.kernel.org/releases-calendar.ics

However, I've noticed that after a while, past events are deleted. So I
was wondering if there is a calendar with the historical data, i.e. the
actual release, -rc, MW etc. dates.

Another thing that would've come in handy is a calendar with the
projected (or past) EOL dates.

I know this sort of info is readily available on the Web (I, for one,
have been referring to Wikipedia [2]) and on Git and the LKML, but in
certain occasions (e.g. bugging managers by copying calendar items to
them), it would come in handy if it were available in iCal format as
well. Does such a thing exist?

[2] https://en.wikipedia.org/wiki/Linux_kernel_version_history

Bence
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

                 reply	other threads:[~2026-10-05 13:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a7c5f068-be55-4df4-a7f2-5a4e44957b3c@arm.com \
    --to=bence.csokas@arm.com \
    --cc=tools@kernel.org \
    /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