dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 28/11/2019
Date: Thu, 28 Nov 2019 20:54:33 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE24BDE57A1@IRSMSX103.ger.corp.intel.com> (raw)

Minutes 21 November 2019

------------------------



Agenda:

* Release Dates

* RC4 Status

* Subtrees

* OvS

* Opens



Participants:

* Arm

* Debian/Microsoft

* Intel

* Marvell

* Mellanox

* NXP

* Red Hat





Release Dates

-------------



* v19.11 dates:

  * RC3 was  released on Wednesday 20 November

    https://mails.dpdk.org/archives/announce/2019-November/000302.html

  * RC4 was released on Tuesday 26 November

    https://mails.dpdk.org/archives/announce/2019-November/000303.html

  * Release planned for Thursday/Friday 28/28 November



* Dates for 20.02 :

  * Proposal/V1:           Wednesday 11 December 2019

  * Integration/Merge/RC1: Wednesday 15 January 2020

  * Release:               Friday    14 February 2020





RC4 Status

----------



* Intel testing complete for RC4. No major issues.

* OvS testing complete.

* Please report all test reports in reply to the RC4 announce message.









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 Thursdays at 8:30 UTC. If you wish to attend just send an email to "John McNamara <john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>>" for the invite.



                 reply	other threads:[~2019-11-28 20:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=B27915DBBA3421428155699D51E4CFE24BDE57A1@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@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
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).