From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Aaron Conole <aconole@redhat.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: [RFC] DPDK Distro Support Policies
Date: Wed, 24 Aug 2022 14:26:54 -0400 [thread overview]
Message-ID: <CAHx6DYChaoT5iQj+WQrD6HcDaydmgcDjHZnhzkD3JO_G8Q7Fwg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Hello Everyone,
At the tech board meeting today I brought up the topic of supported Linux
distros/operating systems. We came up with the following proposal, but want
community feedback before any decision is made. If you want a distro/OS
added, please reply saying so and provide a compelling reason why the
proposed distro/OS should be supported by DPDK, or why you think that more
or fewer versions should be supported. The policy is as follows;
Supported Distros/OSes:
* Alpine
* Arch
* CentOS Stream
* Debian
* Fedora
* Fedora Rawhide
* FreeBSD
* OpenSUSE Leap
* RHEL
* Ubuntu
* Windows
Supported Versions:
Distros or OS versions in General Support will be tested. Support will be
dropped for EOL versions or versions older than 5 years.
RHEL 7 has been granted an expectation to this due to widespread use, and
will continue to be supported until the tech board decides it is out of
widespread use.
Additionally, "binary compatible" distros will have a single distro
selected for testing. For example, RHEL 7 will be treated as providing
testing for CentOS 7.
Owen Hilyard
UNH InterOperability Lab
[-- Attachment #2: Type: text/html, Size: 1698 bytes --]
next reply other threads:[~2022-08-24 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 18:26 Owen Hilyard [this message]
2022-08-24 19:30 ` aisha
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=CAHx6DYChaoT5iQj+WQrD6HcDaydmgcDjHZnhzkD3JO_G8Q7Fwg@mail.gmail.com \
--to=ohilyard@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).