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 26/11/2020
Date: Thu, 26 Nov 2020 15:09:22 +0000
Message-ID: <e2ae80d1-3025-4c64-10e6-9ea283ac8551@intel.com> (raw)

Meeting minutes of 26 November 2020

* Release Dates
* -rc5 status
* Subtrees
* OvS

* Arm
* Broadcom
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat

Release Dates

* v20.11 dates
   * -rc5 is released on      Sunday, 22 November 2020
     * http://inbox.dpdk.org/dev/2457559.JHJOnYWPqN@thomas/
   * Release pushed to         *Friday, 27 November 2020*

* v21.02 dates
   * Proposal/V1:    Sunday, 20 December 2020
   * -rc1:           Friday, 15 January 2021
   * Release:        Friday, 5 February 2021

   * Please send roadmaps, preferably before beginning of the release
     * Thanks to NTT for sending roadmap

-rc5 status

* Ping (form Intel) sent the test repot
   * https://mails.dpdk.org/archives/dev/2020-November/193445.html
   * ... no new critical issue blocked the release is found.

* Red Hat testing looks good
   * https://mails.dpdk.org/archives/dev/2020-November/193416.html

* OvS, 'dpdk-latest' branch, tested with latest DPDK, looks good
   * https://mails.dpdk.org/archives/dev/2020-November/193509.html


* main
   * CI
     * Travis policy for open source projects changed, free slots only
       to open source projects without budget
       * We are out of credit to run more test
         * Need to discuss should we pay for it
           * Currently the budget is used for the UNH lab
       * There is a patch to use github actions
   * Looking to the documentation patches
     * There are lots of them to review
     * David will create a list of patches waiting for review
       * Please support doc reviews
   * Waiting for v2 of dpdk-setup patchset with doc updates
   * Waiting for 21.02 roadmaps
     * Asaf will put a draft discussion on managing the releases

* next-net
   * no update on tree after -rc5

* next-crypto
   * no update

* next-eventdev
   * no update

* next-virtio
   * Done for the release

* next-net-intel
   * no update after -rc5
     * an iavf patch went directly into main not acked by maintainers

* next-net-mlx
   * All good, a few patches went into main directly

* next-net-mrvl
   * no update

* next-net-brcm
   * no update


* Next 18.11 release will be 18.11.11
   * Estimated release date is mid January

* Next 19.11 release will be 19.11.6
   * Expecting a release candidate next week
   * Released tentatively planned for mid December
     * Based on test completion dates and results

* 20.11 LTS
   * Thanks to Kevin volunteered as 20.11 LTS maintainer
     * Kevin will send a roadmap update to document this


* Validated latest DPDK and all looks good

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-11-26 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 15:09 Ferruh Yigit [this message]
2020-11-26 16:13 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2ae80d1-3025-4c64-10e6-9ea283ac8551@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \


* 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 \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

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