From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: [dpdk-announce] release 18.05 delayed
Date: Fri, 13 Apr 2018 00:01:17 +0200 [thread overview]
Message-ID: <16743280.PYHFFin0V3@xps> (raw)
Hi,
The integration deadline is passed by one week, and the first
release candidate is still far from being ready.
This time it is really, really late.
We will try to do this RC1 on the 20th of April, but no guarantee.
Then we may have a lot of new drivers or features to integrate
in the next release candidate. So we need to plan two weeks of work
before releasing the RC2 around the 4th of May, which was the date
initially targeted for the release 18.05.
Usually we need two more weeks of bug fixing in RC3 and RC4,
and few more days of validation before the release.
It means the release will happen on the 23rd of May in the "best case".
During this time, we need everybody's help to finish the reviews.
If you are not involved in reviews or last minute adjustments,
you can start working on new stuff for 18.08, because the preparation
period before the proposal deadline will be tight. We can think about
delaying the proposal deadline for 18.08 by one week (June, 8th).
We should also accept that the 18.08 release might be smaller than usual.
Thanks for understanding and helps
next reply other threads:[~2018-04-12 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 22:01 Thomas Monjalon [this message]
2018-04-23 1:59 ` Thomas Monjalon
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=16743280.PYHFFin0V3@xps \
--to=thomas@monjalon.net \
--cc=announce@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).