From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] DPDK techboard minutes of November 07
Date: Fri, 16 Nov 2018 10:27:02 +0000 [thread overview]
Message-ID: <e345c5c9-672e-54ba-f0cd-163949b71134@intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258010CEB87CE@IRSMSX106.ger.corp.intel.com>
On 15-Nov-18 6:31 PM, Ananyev, Konstantin wrote:
>
> Meeting notes for the DPDK technical board meeting
> held on 2018-11-07
>
> Attendees:
> - Bruce Richardson
> - Ferruh Yigit
> - Konstantin Ananyev
> - Maxime Coquelin
> - Olivier Matz
> - Thomas Monjalon
>
> 0) Informal discussion about current PPC support status
> As brought by Thomas:
> They are not active maintainers for 18.05+ releases for Power 8.
> IBM currently concentrates on 17.11 LTS.
> They plan to be back with 18.11 LTS for Power 9.
> Should we declare Power8 not maintained for 18.11 LTS?
> Another suggestion was to introduce concept of "secondary supported platforms"
> and move PPC to that category
> (by analogy with freebsd tiered platforms:
> https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html).
+1, we can't do anything if there are no maintainers, nor can we declare
a platform as "supported" for an LTS release if there is no commitment
to actually maintain the platform for a number of years.
>
> 1) Next techboard meeting
> - Maxime Coquelin will chair it
>
--
Thanks,
Anatoly
prev parent reply other threads:[~2018-11-16 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 18:31 Ananyev, Konstantin
2018-11-16 10:27 ` Burakov, Anatoly [this message]
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=e345c5c9-672e-54ba-f0cd-163949b71134@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=techboard@dpdk.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).