DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: stable@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 16.11.9 (LTS) patches review and test
Date: Mon, 10 Dec 2018 18:38:58 +0000	[thread overview]
Message-ID: <1544467138.7111.12.camel@debian.org> (raw)
In-Reply-To: <1543508586.5087.45.camel@debian.org>

On Thu, 2018-11-29 at 16:23 +0000, Luca Boccassi wrote:
> Hi all,
> 
> Here is a list of patches targeted for LTS release 16.11.9. Please
> help review and test. The planned date for the final release is
> December the 10th.
> 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 by
> replying to this email.
> 
> This will be the last 16.11 point release. As with all good things,
> it
> must come to an end!
> 
> A release candidate tarball can be found at:
> 
>     https://dpdk.org/browse/dpdk-stable/tag/?id=v16.11.9-rc1
> 
> These patches are located at branch 16.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Luca Boccassi

Hi,

Unfortunately due to the conference and other commitments it was not
possible to have the test results of 16.11.9-rc1 yet, so the final
release will have to be postponed.
Tentative date is a week from now, on December the 17th.

Apologies if this delay causes any issue.

-- 
Kind regards,
Luca Boccassi

  reply	other threads:[~2018-12-10 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 16:23 Luca Boccassi
2018-12-10 18:38 ` Luca Boccassi [this message]
2018-12-13 10:35   ` Luca Boccassi
2018-12-15 10:12     ` Luca Boccassi
2018-12-22 10:15     ` Luca Boccassi
2019-01-24  9:43       ` Luca Boccassi
2019-03-18 12:07         ` Luca Boccassi
2019-03-18 12:07           ` Luca Boccassi
2018-12-13  9:34 ` 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=1544467138.7111.12.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).