DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>, Kevin Traynor <ktraynor@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Yongseok Koh <yskoh@mellanox.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Aaron Conole <aconole@redhat.com>,
	"Walker, Benjamin" <benjamin.walker@intel.com>,
	Jay Rolette <rolette@infinite.io>
Subject: Re: [dpdk-dev] DPDK short term stable maintenance
Date: Tue, 12 Mar 2019 21:51:37 +0100	[thread overview]
Message-ID: <4664304.LLR2pzfpgk@xps> (raw)
In-Reply-To: <834f085314caae4091cfc02c5c904a6efaed3141.camel@debian.org>

12/03/2019 21:46, Luca Boccassi:
> On Tue, 2019-03-12 at 19:12 +0000, Kevin Traynor wrote:
> > So what to do with short term stables? Some choices could be:
> > 
> > - continue with short term stables for n.02/05/08
> > - ad-hoc support for short term stables where community have an
> > interest
> > in a particular one
> > - have a maintainer to backport fixes on a public branch, but have no
> > releases, or have unvalidated/best effort validated releases
> > - no short term stable branches/releases
> > 
> > Probably there's other ideas too. Obviously most of the above would
> > need
> > resources from the community to proceed. One advantage of not having
> > short term stables is that there might be more resources available
> > for
> > maintenance/validation of master and LTS DPDK releases.
[...]
> 
> My 2c is that, unless someone steps up not only for the maintainer role
> but also for the validation effort, we should cancel the short term
> releases.

Yes it looks reasonnable.
So we must question the community at each major release
to know if it will maintained, how long, or not.
If there are volunteers, we must clearly state in the stable release notes
which areas are validated.

  reply	other threads:[~2019-03-12 20:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 19:12 Kevin Traynor
2019-03-12 20:46 ` Luca Boccassi
2019-03-12 20:51   ` Thomas Monjalon [this message]
2019-03-12 23:49     ` Stephen Hemminger
2019-03-22 10:45   ` Kevin Traynor
2019-03-22 10:45     ` Kevin Traynor

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=4664304.LLR2pzfpgk@xps \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=rolette@infinite.io \
    --cc=yskoh@mellanox.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.
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).