From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] Proposed dates for 19.02 release
Date: Thu, 22 Nov 2018 11:19:03 +0100 [thread overview]
Message-ID: <1637579.lLCQyC1IBu@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F43E7B6@IRSMSX103.ger.corp.intel.com>
18/10/2018 14:50, Mcnamara, John:
> Hi,
>
> There are two constraints within the 19.02 release timeframe this year:
>
> * Christmas/New Year's holidays
> * Chinese Spring Festival Holiday 4th-10th February (with some people out
> the week before as well). Note this is much earlier than in previous years.
>
> Since the majority of the testing is done by the Intel team in China we
> would need to complete all testing before the end of January. Working back
> from this and avoiding having people work over Christmas week we would have
> the following dates:
>
> * Proposal deadline Friday 23 November 2018
> * Merge deadline Friday 14 December 2018
> * RC1 release Friday 21 December 2018
> * RCx + Testing Friday 25 January 2019
> * Release Friday 1 February 2019
>
> In order to meet these deadlines we would have to reduce the size/scope
> of the release.
>
> So the proposal would be that 19.02 is a smaller release and that we would
> prioritize 19.05 as a larger release.
>
> Note, this also means that the Proposal deadline in only about 1 month away
> and that it may occur before the 18.11 is released.
>
> If there are major objections or people have better ideas on how to schedule
> the release then let us know.
As discussed in release meeting today, we will move the proposal deadline
by few days (Thursday 29th) to make it happen after 18.11 release.
prev parent reply other threads:[~2018-11-22 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 12:50 Mcnamara, John
2018-11-22 10:19 ` 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=1637579.lLCQyC1IBu@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).