From: Luca Boccassi <bluca@debian.org>
To: dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 18.02.2 patches review and test
Date: Fri, 15 Jun 2018 12:00:01 +0100 [thread overview]
Message-ID: <1529060401.6554.64.camel@debian.org> (raw)
In-Reply-To: <1528449386.6997.119.camel@debian.org>
On Fri, 2018-06-08 at 10:16 +0100, Luca Boccassi wrote:
> On Mon, 2018-06-04 at 09:58 +0100, Luca Boccassi wrote:
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 18.02.2.
> > Please
> > help review and test. The planned date for the final release is
> > Thursday,
> > the 14th of June. Before that, please shout if anyone has
> > objections
> > with these
> > patches being applied.
> >
> > Also for the companies committed to running regression tests,
> > please run the tests and report any issue before the release date.
> >
> > These patches are located at branch 18.02 of dpdk-stable repo:
> > https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Luca Boccassi
>
> Hi,
>
> The release date for 18.02.2 is being postponed by one day to Friday
> the 15th to due to unforeseen delays in some regression tests.
> Apologies for the inconvenience.
The regression tests from Intel were all green, so the release will
happen later today.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-06-15 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 8:58 Luca Boccassi
2018-06-04 18:35 ` Luca Boccassi
2018-06-07 23:10 ` Raslan Darawsheh
2018-06-08 8:23 ` [dpdk-dev] [dpdk-stable] " Luca Boccassi
2018-06-08 9:16 ` [dpdk-dev] " Luca Boccassi
2018-06-08 18:28 ` Ray Cai
2018-06-09 10:31 ` Luca Boccassi
2018-06-13 6:56 ` [dpdk-dev] [dpdk-stable] " Marco Varlese
2018-06-13 9:28 ` Luca Boccassi
2018-06-15 11:00 ` Luca Boccassi [this message]
2018-06-11 12:28 ` [dpdk-dev] " Shreyansh Jain
2018-06-11 12:46 ` 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=1529060401.6554.64.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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).