DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 6/08/2020
Date: Thu, 6 Aug 2020 14:51:48 +0100
Message-ID: <c12f6492-dc1e-0f26-3a56-28ef61675f87@intel.com> (raw)

Minutes 6 August 2020
---------------------

Agenda:
* Release Dates
* -rc3/-rc4 status
* Subtrees
* LTS
* OvS

Participants:
* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* NXP
* Red Hat


Release Dates
-------------

* v20.08 dates:
  * -rc3 is released on Thursday, 30 July 2020
    * http://inbox.dpdk.org/dev/11727811.Rr6YEUNczV@thomas/
  * -rc4 is released on Wednesday, 5 August 2020
    * http://inbox.dpdk.org/dev/4161866.7AHn6HmuGJ@thomas/
  * Release         Friday, 7 August 2020

* v20.11 proposal dates, please comment:
  * Proposal/V1:    Friday, 11 September 2020
  * -rc1:           Friday, 9 October 2020
  * -rc2:           Friday, 23 October 2020
  * Release:        Friday, 13 November 2020

  * The dates are still not finalized, we need to discuss this offline and
    define dates as soon as possible, please comment.

  * Please remember to send roadmap for 20.11, non received yet.


-rc3/-rc4 status
----------------

* Intel early -rc4 test result looks good
  * Fixes for two critical issues from -rc3 verified

* Red Hat -rc3 test result in mail list
  * No issue reported, all looks good


Subtrees
--------

* main
  * Only documentation updates after this point
    * John will help on release notes updates/review
  * There are lots of deprecation notices to review for the release
  * Tested platform patch form Mellanox merged, good to have similar report from
    all vendors for release notes
    * https://patches.dpdk.org/patch/74994/
    * https://patches.dpdk.org/patch/75198/
  * Please review roadmap website update patch
    * http://patchwork.dpdk.org/patch/75181/
  * Please all maintainers cleanup the patchwork before release

* next-net
  * No update after -rc3
  * Relevant patches directly merged to main repo by Thomas
  * There are deprecation notices to review for release

* next-crypto
  * No update on tree
  * Two/Three deprecation notices waiting for merge

* next-eventdev
  * No update on tree
  * There are deprecation notices in backlog
    * The one adding reserved fields may be dropped

* next-virtio
  * Done for release
  * vdpa patches for -rc4 merged directly to main repo
  * There is a Vhost dequeue zero-copy removal deprecation notice
    * https://patches.dpdk.org/patch/75147/
    * Need to sync with OvS community related to it
  * Another deprecation notice for rte_dev_probe() change
    * https://patches.dpdk.org/patch/72170/
    * Thomas & Maxime will synchronize offline on it

* next-net-mlx, next-net-intel, next-net-brcm
  * Patches merged directly to main repo


LTS
---

* 19.11.4 work is going on
  * Some patches are backported, email sent, please review

* 18.11.10 work is going on
  * Some patches are backported


OvS
---

* 2.14 release trending for 17 August



DPDK Release Status Meetings
============================

The DPDK Release Status Meeting is intended for DPDK Committers to discuss the
status of the master tree and sub-trees, and for project managers to track
progress or milestone dates.

The meeting occurs on every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK

If you wish to attend just send an email to
"John McNamara <john.mcnamara@intel.com>" for the invite.

             reply	other threads:[~2020-08-06 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 13:51 Ferruh Yigit [this message]
2020-08-06 14:55 ` Thomas Monjalon
2020-08-06 15:52   ` Ajit Khaparde
2020-08-06 18:14     ` Honnappa Nagarahalli
2020-08-07  4:52       ` Hemant Agrawal
2020-08-06 15:08 ` David Marchand

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=c12f6492-dc1e-0f26-3a56-28ef61675f87@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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 patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/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 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


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