From: Thomas Monjalon <thomas@monjalon.net>
To: Luca Boccassi <bluca@debian.org>, yliu@fridaylinux.org
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] DPDK 17.11 LTS
Date: Fri, 06 Oct 2017 19:12:45 +0200 [thread overview]
Message-ID: <2385365.XUACAUbIaV@xps> (raw)
In-Reply-To: <1507307118.24598.3.camel@debian.org>
06/10/2017 18:25, Luca Boccassi:
> On Fri, 2017-10-06 at 16:05 +0000, Mcnamara, John wrote:
> > Hi,
> >
> > At the recent DPDK 2017 Userspace in Dublin it was agreed that we
> > should have a DPDK 17.11 LTS with 2 year support that would run in
> > parallel with the DPDK 16.11 LTS.
> >
> > However, if order for this to happen the community will have to
> > provide a maintainer, either for 17.11 LTS or for 16.11 LTS (to allow
> > Yuanhan to move from 16.11 LTS maintenance to 17.11 LTS maintenance).
> >
> > Ideally this person should come from one of the OSVs. Either way if
> > we don't get a volunteer we won't have a 17.11 LTS.
> >
> > Volunteers please step forward.
> >
> > John
>
> Hello John,
>
> I was just about to write you :-)
>
> I am available to volunteer. I've just got permission from AT&T
> management to dedicate some working hours every week to the project
> (this is the reason why I didn't say anything on the spot - I needed to
> ask first due to the time requirements).
>
> I am fine with either 16.11 or 17.11, whichever Yuanhan prefers.
>
> Thanks!
Thanks a lot Luca, and welcome :)
You will have to send me a public SSH key.
Yuanhan, how do you prefer to split the workload?
next prev parent reply other threads:[~2017-10-06 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 16:05 Mcnamara, John
2017-10-06 16:25 ` Luca Boccassi
2017-10-06 17:12 ` Thomas Monjalon [this message]
2017-10-09 1:44 ` Yuanhan Liu
2017-10-09 7:49 ` Thomas Monjalon
2017-10-09 8:01 ` Yuanhan Liu
2017-10-09 9:43 ` Luca Boccassi
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=2385365.XUACAUbIaV@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=yliu@fridaylinux.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).