From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] Suggestions for the dpdk stable tree
Date: Fri, 20 May 2016 17:54:06 +0200 [thread overview]
Message-ID: <CAATJJ0J25FVJAjhDFv_Df3xHmf_5m9e0VH0fMQd=WbgTK99dLA@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE202560ACB@IRSMSX103.ger.corp.intel.com>
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.
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
On Fri, May 20, 2016 at 4:49 PM, Mcnamara, John <john.mcnamara@intel.com>
wrote:
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Christian Ehrhardt
> > Sent: Friday, May 20, 2016 9:07 AM
> > To: dev <dev@dpdk.org>; Stephen Hemminger <stephen@networkplumber.org>
> > Subject: Re: [dpdk-dev] Suggestions for the dpdk stable tree
> >
> > Hi,
> > I guess over time/releases less people mind the 2.2-stable.
> > But I still see a lot of people referring to 2.2 - so why not giving this
> > thread a ping again.
> >
> > ack / nack / opinions ?
>
> Hi Christian,
>
> We are interested in having a LTS/Stable tree.
>
> We have been looking at identifying a maintainer and validation engineer
> internally to support the effort but haven't be able to finalize that. Once
> we do we will come back to the mailing list with a proposal and a request
> for comments.
>
> We would probably be looking at 16.04 or even 16.07 as the basis for the
> LTS at this stage.
>
> It would be great if we could get support from you or others as well.
>
> John.
> --
>
>
next prev parent reply other threads:[~2016-05-20 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 7:14 Christian Ehrhardt
2016-05-20 8:07 ` Christian Ehrhardt
2016-05-20 14:49 ` Mcnamara, John
2016-05-20 15:54 ` Christian Ehrhardt [this message]
2016-05-20 21:02 ` Markos Chandras
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='CAATJJ0J25FVJAjhDFv_Df3xHmf_5m9e0VH0fMQd=WbgTK99dLA@mail.gmail.com' \
--to=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 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).