From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 27C571B14D for ; Thu, 22 Nov 2018 11:19:06 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BD92121F67; Thu, 22 Nov 2018 05:19:05 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 22 Nov 2018 05:19:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=aST3Wq187DUumqObzV/tWRt4afHb+KOaTqCOeP4AXcc=; b=n3cugre8RsN+ wtTIZCroXpiMCyBZw1C/0bHUYBaD2L8knk22M7r6ADVpShVIYweNziRUOrwi5dC+ opan9mWNrxdWMhLjeSWw8ZEGPcTA3BniErcy+Y9u/opYZea++0aOmXes1v2yvfmR 0ERxAhzBF4KZVHU1B52kRK5mHijiAqk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=aST3Wq187DUumqObzV/tWRt4afHb+KOaTqCOeP4AX cc=; b=jGrh4z8fG92XEstJMcwq8KOABQcypFofT+cxR6v2XbO7p8TkxBc4IHES6 vrUz9q5ewUHCPL4Lci3EflIpHNdbuSLtm4JfJzVoWHv7ffpy3bE6GsKJh8TR4ubs 9gVTUDE59whjOYJlZcupWTtO/rEDeT0XoFEt8j58ZORPGQpmcsvUF4nVByMH/V3q KqXE1dNkKUYa+RNJz5fVTeyWYOid067hPBXfzV3u2/lG8Vw1NkkpDb1mdhaVjLFm IM0CXfwuYpPEmF0x7PBwKCQpoHMYbzRtqDph4kTQLGmzL2L2kUToE1IxfIrULW5J u304/d2NGGUVobmurIoPfdZ8SViFw== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BF64AE48FA; Thu, 22 Nov 2018 05:19:04 -0500 (EST) From: Thomas Monjalon To: dev@dpdk.org Cc: "Mcnamara, John" Date: Thu, 22 Nov 2018 11:19:03 +0100 Message-ID: <1637579.lLCQyC1IBu@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Proposed dates for 19.02 release X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2018 10:19:06 -0000 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.