From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, John McNamara <john.mcnamara@intel.com>,
Qian Xu <qian.q.xu@intel.com>
Subject: Re: [dpdk-dev] Proposed dates for 20.02 release
Date: Thu, 07 Nov 2019 14:58:28 +0100 [thread overview]
Message-ID: <1634476.ZoJZR0r5cf@xps> (raw)
In-Reply-To: <f6b216ea-19a8-9935-0563-0c16ccd32bc0@linux.intel.com>
07/11/2019 14:07, Yigit, Ferruh:
> On 9/11/2019 9:27 PM, Thomas Monjalon wrote:
> > 11/09/2019 19:55, Ferruh Yigit:
> >> 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]
> >
> > 10 January for integration deadline is short.
> > And we should give more time after China holiday.
> > I suggest to shift rc1 and final release dates by one week.
> >
> >
>
> It seems there is no objection to shift, also in new dates Cathal suggested
> pulling rc1 from Friday 17 to Wednesday 15 January, to give enough time to PRC
> team before holidays, so final proposed dates are as following:
>
> Proposal/V1: 6 December
> Integration/Merge/RC1: 15 January
> Release: 14 February
I agree with these dates.
prev parent reply other threads:[~2019-11-07 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:55 Ferruh Yigit
2019-09-11 20:27 ` Thomas Monjalon
2019-11-07 13:07 ` Yigit, Ferruh
2019-11-07 13:58 ` Thomas Monjalon [this message]
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=1634476.ZoJZR0r5cf@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@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).