DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Qian Xu <qian.q.xu@intel.com>
Subject: [dpdk-dev] Proposed dates for 20.02 release
Date: Wed, 11 Sep 2019 18:55:52 +0100	[thread overview]
Message-ID: <b4dc9233-b052-3877-c020-0a26407368a6@intel.com> (raw)

Hi,

We need input to plan the 20.02 release dates.

There are two constraints for the .02 releases which makes it harder to plan,
the Christmas/New Year's holidays and Chinese Spring Festival Holiday.

This years schedule for them is:

* Christmas/New Year's:
  25,26 December; 1 January. In practice many people will be on leave on WW52.

* Chinese Spring Festival Holiday:
  24-30 January (inclusive).


According above dates proposed dates are:

Proposal/V1:		6 December (4 weeks)				[WW49]
Integration/Merge/RC1:	10 January (5 weeks including Christmas)	[WW2]
Release:		7 February (4 weeks including Spring Festival)	[WW6]


Please comment if you have any concerns or objections on the proposed dates.

The dates are finalized in "Release Status Meeting" which is open to the
community, anyone wants to discuss further can attend those meetings [1].


Thanks,
ferruh

[1]
Meeting details are at the bottom of the notes:
https://mails.dpdk.org/archives/dev/2019-September/142490.html

             reply	other threads:[~2019-09-11 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 17:55 Ferruh Yigit [this message]
2019-09-11 20:27 ` Thomas Monjalon
2019-11-07 13:07   ` Yigit, Ferruh
2019-11-07 13:58     ` 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=b4dc9233-b052-3877-c020-0a26407368a6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=qian.q.xu@intel.com \
    --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).