All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Luca Boccassi <bluca@debian.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Regression tests for stable releases from companies	involved in DPDK
Date: Mon, 4 Jun 2018 05:24:29 +0000	[thread overview]
Message-ID: <HE1PR0402MB27809AE4B430B1AE31E983EE90670@HE1PR0402MB2780.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1527762399.6997.44.camel@debian.org>

Hello Luca

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Luca Boccassi
> Sent: Thursday, May 31, 2018 3:57 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; thomas@monjalon.net
> Subject: [dpdk-dev] Regression tests for stable releases from companies
> involved in DPDK
> 
> Hello all,
> 
> At this morning's release meeting (minutes coming soon from John), we
> briefly discussed the state of the regression testing for stable
> releases and agreed we need to formalise the process.
> 
> At the moment we have a firm commitment from Intel and Mellanox to test
> all stable branches (and if I heard correctly from NXP as well? Please

Yes, I confirmed that on call on behalf of NXP. But...

> confirm!). AT&T committed to run regressions on the 16.11 branch.

Not until 17.05 did NXP's first driver started appearing in the DPDK upstream releases. Somehow, I misunderstood your request for 16.11 with 17.11 stable.

[...]

-
Shreyansh

  parent reply	other threads:[~2018-06-04  5:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 10:26 Regression tests for stable releases from companies involved in DPDK Luca Boccassi
2018-06-01  4:38 ` [dpdk-stable] " Christian Ehrhardt
2018-06-01  9:57   ` Luca Boccassi
2018-06-01  8:17 ` Marco Varlese
2018-06-01  9:56   ` Luca Boccassi
2018-06-01 11:04     ` Marco Varlese
2018-06-04  5:24 ` Shreyansh Jain [this message]
2018-06-04  8:38   ` [dpdk-stable] " 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=HE1PR0402MB27809AE4B430B1AE31E983EE90670@HE1PR0402MB2780.eurprd04.prod.outlook.com \
    --to=shreyansh.jain@nxp.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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.