From: Thomas Monjalon <thomas@monjalon.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Proposed schedule dates for DPDK 17.08, 17.11 and 18.02
Date: Wed, 17 May 2017 15:02:14 +0200 [thread overview]
Message-ID: <1668093.ZiKoiLqDrf@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2332C79E4@IRSMSX103.ger.corp.intel.com>
Hi,
04/05/2017 18:52, Mcnamara, John:
> The current 17.08 schedule dates are:
>
> 17.08
> * Proposal deadline: May 28, 2017
> * Integration deadline: June 29, 2017
> * Release: August 1, 2017
I think these dates are good and must be strictly respected.
It would be very bad (at least for me) to release later in August.
> The following are proposed dates for 17.11 and 18.02.
>
> 17.11
> * Proposal deadline: August 25, 2017
As we can see in the following picture [1],
we work less in August and tend to send the proposals at the last minute.
[1] https://s12.postimg.org/g9uluz9u5/patchesv1.png
I don't know what can be done to avoid having hard days of reviews
after the August deadline.
Should we cut this period before or let a bit more days?
> * Integration deadline: September 29, 2017
> * Release: November 2, 2017
I'm OK for these ones.
> 18.02
> * Proposal deadline: November 24, 2017
> * Integration deadline: December 29, 2017
The Christmas / New Year holidays will be from Dec 25 to Jan 1.
I think we could move the integration deadline to Jan 5.
> * Release: February 2, 2018
The Chinese Spring Festival will be from Feb 15 to 21.
So we have a good margin.
> These dates need to be discussed/agreed in the community since there are a
> lot of different holidays in these periods: August holidays, Christmas,
> New Year, Spring Festival.
next prev parent reply other threads:[~2017-05-17 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 11:32 Mcnamara, John
2017-05-04 16:52 ` Mcnamara, John
2017-05-17 13:02 ` Thomas Monjalon [this message]
2017-05-30 20:29 ` Thomas Monjalon
2017-06-01 8:58 ` Mcnamara, John
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=1668093.ZiKoiLqDrf@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/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).