All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Maxime Coquelin <mcoqueli@redhat.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	david.marchand@redhat.com
Subject: Re: [PATCH] doc: no longer support end of life CentOS versions
Date: Tue, 19 Nov 2024 16:34:24 +0100	[thread overview]
Message-ID: <2377659.n0HT0TaD9V@thomas> (raw)
In-Reply-To: <20240730234228.89967-1-stephen@networkplumber.org>

31/07/2024 01:40, Stephen Hemminger:
> The CentOS Project has shifted focus from CentOS Linux to CentOS Stream.
> Both CentOS 7 and 8 are now end of life (EOL).
> 
> 	CentOS Linux 7 EOL: 2024-06-30
> 	CentOS Linux 8 EOL: 2021-12-31
> 	CentOS Stream 8 EOL: 2024-05-31
> 
> Update the documentation and release notes. There is no explicit
> test in the build process that would block these older versions
> but any bug reports or problems will rejected as invalid.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

We need an ack from Red Hat maintainers.
Adding some Cc.

>      The kernel version required is based on the oldest long term stable kernel available
>      at kernel.org when the DPDK version is in development.
> -    Compatibility for recent distribution kernels will be kept, notably RHEL/CentOS 7.
> +    Compatibility is maintained for currently supported enterprise distribution kernels
> +    such as RHEL 8 (which uses 4.18 kernel).

I prefer the previous wording: "recent distribution kernels".
And I prefer not talking about the kernel version given it is largely patched with backports.

[...]
> +* **Removed support guarantee for CentOS 7 and 8.**
> +
> +  DPDK can no longer guarantee support for older CentOS releases.
> +  CentOS Linux 7 reached end of life (EOL) on 30 June 2024.
> +  CentOS Linux 8 stream was end of life on 31 May 2024.




  reply	other threads:[~2024-11-19 15:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 16:57 [PATCH] doc: update minimum Linux kernel version Stephen Hemminger
2024-01-11  9:18 ` Morten Brørup
2024-01-11 18:48   ` Aaron Conole
2024-01-11 19:02   ` Patrick Robb
2024-01-11 19:26     ` Morten Brørup
2024-01-11 19:50       ` Patrick Robb
2024-01-11 19:54       ` Stephen Hemminger
2024-01-11 22:38         ` Morten Brørup
2024-02-16  3:05           ` Stephen Hemminger
2024-02-16  8:29             ` Morten Brørup
2024-02-16 17:22               ` Stephen Hemminger
2024-02-16 17:42               ` Stephen Hemminger
2024-02-17 19:48                 ` Patrick Robb
2024-07-29 20:07                 ` Thomas Monjalon
2024-07-30 23:27                   ` Stephen Hemminger
2024-07-30 23:40                   ` [PATCH] doc: no longer support end of life CentOS versions Stephen Hemminger
2024-11-19 15:34                     ` Thomas Monjalon [this message]
2024-11-19 18:40                       ` Stephen Hemminger
2024-11-19 19:38                         ` Thomas Monjalon
2024-11-19 23:09                     ` [PATCH v2] " Stephen Hemminger
2025-07-21 12:40                       ` Kevin Traynor
2025-07-21 12:50                       ` David Marchand

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=2377659.n0HT0TaD9V@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --cc=mcoqueli@redhat.com \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.