unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "code@ceephax.com" <code@ceephax.com>, 53414@debbugs.gnu.org
Subject: [bug#53414] [PATCH] update Node LTS to 16.13.2
Date: Fri, 25 Feb 2022 13:38:02 +0100	[thread overview]
Message-ID: <fdec0107b123a00236eba5c08ea73e219f685d09.camel@telenet.be> (raw)
In-Reply-To: <4ce7393f-d9fe-4cf2-af4c-de154f977be9@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

code@ceephax.com schreef op vr 25-02-2022 om 11:24 [+0000]:
> It will be end-of-life in two months.  More generally, I don't see
> the
End of life is 	2023-04-30

I looked at the wrong version (v12 instead of v14), it's a year and two
months instead of two months.  Still, the latest LTS (v16) seems better
to me since it is newer and will be supported for longer.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-02-25 13:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 15:11 [bug#53414] [PATCH] update Node LTS to 16.13.2 zamfofex
2022-02-23 13:13 ` code
2022-02-25 11:07   ` Maxime Devos
2022-02-25 11:24     ` code
2022-02-25 12:38       ` Maxime Devos [this message]
2022-02-25 13:09 ` Attila Lendvai
2022-02-25 15:59   ` Maxime Devos
2022-02-25 16:31     ` Pierre Langlois
2022-02-25 17:22       ` Maxime Devos
2022-05-02  6:10         ` Ryan Sundberg via Guix-patches via
2022-05-15 13:45           ` Pierre Langlois
2022-06-09  6:39             ` Ryan Sundberg via Guix-patches via
2022-06-09 20:49               ` Maxime Devos
2022-06-09 20:50               ` Maxime Devos
2022-06-09 20:53               ` Maxime Devos
2022-06-09 20:55               ` Maxime Devos
2022-06-09 21:03               ` Maxime Devos
2022-11-16 23:23                 ` Mekeor Melire

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=fdec0107b123a00236eba5c08ea73e219f685d09.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53414@debbugs.gnu.org \
    --cc=code@ceephax.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).