From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: Proposed dates for 19.02 release
Date: Thu, 22 Nov 2018 11:19:03 +0100
Message-ID: <1637579.lLCQyC1IBu@xps>
References: <B27915DBBA3421428155699D51E4CFE23F43E7B6@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: "Mcnamara, John" <john.mcnamara@intel.com>
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 27C571B14D
 for <dev@dpdk.org>; Thu, 22 Nov 2018 11:19:06 +0100 (CET)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F43E7B6@IRSMSX103.ger.corp.intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.