From: Markos Chandras <mchandras@suse.de>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: Suggestions for the dpdk stable tree
Date: Fri, 20 May 2016 22:02:13 +0100 [thread overview]
Message-ID: <573F7B55.8050301@suse.de> (raw)
In-Reply-To: <CAATJJ0J25FVJAjhDFv_Df3xHmf_5m9e0VH0fMQd=WbgTK99dLA@mail.gmail.com>
Hi,
On 05/20/2016 04:54 PM, Christian Ehrhardt wrote:
> Hi,
> it would be great to have an actively maintained LTS release.
>
> Clearly all us "Distribution People" like Panu, Me and a few others should
> - whenever bugs are identified as potential backports - start the
> discussion.
> And having an stable-maintainer on the other end sounds great.
>
> The active maintainer you provide would do the usual auto-backport of fixes
> once they come up upstream.
> While us others would provide input from real exposure to users that flows
> in via bug tracking tools.
>
> Looking forward for you coming back to the list once you have found one.
Yes that sounds like a very good idea indeed!
--
markos
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
next prev parent reply other threads:[~2016-05-20 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 7:14 Suggestions for the dpdk stable tree Christian Ehrhardt
2016-05-20 8:07 ` Christian Ehrhardt
2016-05-20 14:49 ` Mcnamara, John
2016-05-20 15:54 ` Christian Ehrhardt
2016-05-20 21:02 ` Markos Chandras [this message]
2016-05-23 2:21 ` Yuanhan Liu
2016-06-01 19:01 ` Mcnamara, John
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=573F7B55.8050301@suse.de \
--to=mchandras@suse.de \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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.