DPDK patches and discussions
 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 20:38:53 +0100	[thread overview]
Message-ID: <39369677.J2Yia2DhmK@thomas> (raw)
In-Reply-To: <20241119104030.1f3733a4@hermes.local>

19/11/2024 19:40, Stephen Hemminger:
> On Tue, 19 Nov 2024 16:34:24 +0100
> Thomas Monjalon <thomas@monjalon.net> wrote:
> 
> > 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".
> 
> The choice of wording was to highlight that what matters is large distributions;
> we don't care directly about embedded (Yocto et al) or fringe stuff (Gentoo, Alma, Alpine, ...)
> which have their own cadence.

We support Alpine for containers usage.

> > And I prefer not talking about the kernel version given it is largely patched with backports.
> 
> Good point.





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

Thread overview: 20+ 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
2024-11-19 18:40                       ` Stephen Hemminger
2024-11-19 19:38                         ` Thomas Monjalon [this message]
2024-11-19 23:09                     ` [PATCH v2] " Stephen Hemminger

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=39369677.J2Yia2DhmK@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 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).