DPDK announcements
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: Re: [dpdk-announce] release 18.05 delayed
Date: Mon, 23 Apr 2018 03:59:57 +0200
Message-ID: <4331565.BVefF9EF6h@xps> (raw)
In-Reply-To: <16743280.PYHFFin0V3@xps>

Hi,

Please find an update of the release status, inline below.

13/04/2018 00:01, Thomas Monjalon:
> 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.

.. no guarantee, indeed.
There are 742 patches in master, 56 in next-net, 68 in next-crypto,
and a lot more not yet merged.
List of remaining significant patches for RC1:

missing in next-net
	- runtime queue setup
	- new VXLAN and MPLS tunnels
	- generic IP/UDP tunnel offloads
	- tunnel encap/decap
	- flow API related fixes
	- flow API overhaul for switch offloads
	- rte_flow extension for vSwitch
	- switching devices representation
missing in master:
	- secondary vdev
	- replace calls to rte_panic
	- control threads
	- symbolic log levels
	- devargs cleanup
	- device querying
	- mbuf external
	- mempool bucket driver

> 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.

List of major patches for RC2:
	- compressdev
	- DPAA2 QDMA raw driver
	- DPAA2 Command Interface raw driver
	- Hyper-V bus and NetVSC PMD
	- Intel FPGA
	- BPF

> 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.

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 22:01 Thomas Monjalon
2018-04-23  1:59 ` Thomas Monjalon [this message]

Reply instructions:

You may reply publically 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=4331565.BVefF9EF6h@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

DPDK announcements

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/announce/0 announce/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 announce announce/ http://inbox.dpdk.org/announce \
		announce@dpdk.org
	public-inbox-index announce


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.announce


AGPL code for this site: git clone https://public-inbox.org/ public-inbox