From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "web@dpdk.org" <web@dpdk.org>,
"Stokes, Ian" <ian.stokes@intel.com>,
"Kevin Traynor" <ktraynor@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Luca Boccassi" <bluca@debian.org>,
Xueming Li <xuemingl@nvidia.com>,
"David Marchand" <dmarchan@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
"Raslan Darawsheh" <rasland@nvidia.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Ali Alnubani <alialnu@nvidia.com>,
David Christensen <drc@linux.vnet.ibm.com>,
"Walker, Benjamin" <benjamin.walker@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"pingx.yu@intel.com" <pingx.yu@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
"Govindharajan, Hariprasad" <hariprasad.govindharajan@intel.com>
Subject: RE: [PATCH 2/2] Extend 19.11.x support period to 3 years
Date: Tue, 14 Dec 2021 08:02:41 +0000 [thread overview]
Message-ID: <DM6PR11MB3227DD3B22F1B766DF41B8E8FC759@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAATJJ0L+Cdw51fYTHzx=CukMsOS9kXrNoRO2LWKy8_D6_+akGQ@mail.gmail.com>
> -----Original Message-----
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Sent: Tuesday, December 14, 2021 7:55 AM
>...
> <hariprasad.govindharajan@intel.com>
> Subject: Re: [PATCH 2/2] Extend 19.11.x support period to 3 years
>
> On Wed, Dec 8, 2021 at 5:16 PM Mcnamara, John <john.mcnamara@intel.com>
> wrote:
> >
> > > -----Original Message-----
> > > From: christian.ehrhardt@canonical.com
> > > <christian.ehrhardt@canonical.com>
> > > Sent: Thursday, December 2, 2021 10:18 AM
> > > Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > > Subject: [PATCH 2/2] Extend 19.11.x support period to 3 years
> > >
> > > From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > >
> > > It was discussed in various places by now, along with the switch of
> > > the main development branch to three per year we also want to extend
> > > the lifetime of the LTS releases.
> >
> > Hi Christian,
> >
> > Zhaoyan and the Intel System Test team agree to test the additional year
> 3 releases.
> >
> > John
> >
> > Acked-by: John McNamara <john.mcnamara@intel.com>
>
> @Mcnamara, John - Intel usually submits two test results.
> One like http://mails.dpdk.org/archives/stable/2021-August/033130.html
> And one separately for "Intel(R) Testing with Open vSwitch" like
> http://mails.dpdk.org/archives/stable/2021-June/031702.html
> Does the above commitment include both?
Yes. We will commit to both.
John
next prev parent reply other threads:[~2021-12-14 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 10:18 [PATCH 0/2] Extend stable coverage on the roadmap christian.ehrhardt
2021-12-02 10:18 ` [PATCH 1/2] Delay release of 19.11.11 christian.ehrhardt
2021-12-03 12:27 ` Luca Boccassi
2021-12-03 14:17 ` Kevin Traynor
2021-12-02 10:18 ` [PATCH 2/2] Extend 19.11.x support period to 3 years christian.ehrhardt
2021-12-03 12:28 ` Luca Boccassi
2021-12-03 14:17 ` Kevin Traynor
2021-12-08 16:16 ` Mcnamara, John
2021-12-14 7:55 ` Christian Ehrhardt
2021-12-14 8:02 ` Mcnamara, John [this message]
2021-12-14 8:38 ` Ali Alnubani
2021-12-16 10:56 ` Pei Zhang
2021-12-16 11:12 ` Christian Ehrhardt
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=DM6PR11MB3227DD3B22F1B766DF41B8E8FC759@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dmarchan@redhat.com \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=juhlee@microsoft.com \
--cc=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=xuemingl@nvidia.com \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.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).