From: Luca Boccassi <bluca@debian.org>
To: dpdk stable <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 17.11.10 (LTS) patches review and test
Date: Thu, 30 Jan 2020 10:08:06 +0000 [thread overview]
Message-ID: <2f51123561d963631215bba308f06158fa0da806.camel@debian.org> (raw)
In-Reply-To: <630ab48b958f4bea1c31e83b8a200f236cd6fcff.camel@debian.org>
On Mon, 2020-01-13 at 12:47 +0000, Luca Boccassi wrote:
> Hi all,
>
> Here is a list of patches targeted for LTS release 17.11.10.
> This will be the last 17.11 release.
>
> The planned date for the final release is the 30th of January.
>
> Please help with testing and validation of your use cases and report
> any issues/results with reply-all to this mail. For the final release
> the fixes and reported validations will be added to the release
> notes.
>
> A release candidate tarball can be found at:
>
>
> https://dpdk.org/browse/dpdk-stable/tag/?id=v17.11.10-rc1
>
>
> These patches are located at branch 17.11 of dpdk-stable repo:
>
> https://dpdk.org/browse/dpdk-stable/
>
>
> Thanks.
>
> Luca Boccassi
Hi,
We are still waiting to solve 2 issues highlighted during validation,
so we need to postpone.
New proposed target is February the 14th.
Apologies for any issue it might cause.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-01-30 10:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 12:47 Luca Boccassi
2020-01-17 2:52 ` Pei Zhang
2020-01-17 10:44 ` Luca Boccassi
2020-01-22 5:27 ` Yu, PingX
2020-01-22 11:37 ` Luca Boccassi
2020-01-22 14:17 ` [dpdk-dev] [dpdk-stable] " Kevin Traynor
2020-01-22 16:07 ` Luca Boccassi
2020-01-22 16:06 ` [dpdk-dev] " Ali Alnubani
2020-01-22 16:34 ` Luca Boccassi
2020-01-23 11:05 ` Luca Boccassi
2020-01-26 14:58 ` Ali Alnubani
2020-01-27 10:41 ` Luca Boccassi
2020-01-30 10:08 ` Luca Boccassi [this message]
2020-01-30 15:01 ` Stokes, Ian
2020-01-30 15:25 ` Luca Boccassi
2020-02-15 11:21 ` Luca Boccassi
2020-02-20 10:00 ` Luca Boccassi
2020-02-20 11:37 ` Trahe, Fiona
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=2f51123561d963631215bba308f06158fa0da806.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).