From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A671BA2EEB for ; Wed, 11 Sep 2019 22:27:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B03D01E565; Wed, 11 Sep 2019 22:27:54 +0200 (CEST) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by dpdk.org (Postfix) with ESMTP id 2470C1D423 for ; Wed, 11 Sep 2019 22:27:53 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 859FC514; Wed, 11 Sep 2019 16:27:50 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 11 Sep 2019 16:27:50 -0400 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=TkCGVZSf7EqWO4NPQmv8H8UlIqV2bMyFDh41lKrhJwQ=; b=kUXqUR0zC1m/ LzJCzNM/UcIhvb2T6h96Qb0Eb93J1Zac1a7tuzgJNvjqSrIibAgzJ+6UYWFUgojl x1xhD229T+mzSgf3zl8t5D94EsUcBrJ1Gta7MJeXeF76WK2byw7WB0DCnpwID1I9 8W49oURPlyfEU5nq+w3iYBlk4BbfqJY= 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=fm3; bh=TkCGVZSf7EqWO4NPQmv8H8UlIqV2bMyFDh41lKrhJ wQ=; b=Lq64dgLE6DdW2viAYo3LbGkJK5asVPauvC3r7q89SrmLTNOMKaq/xFihD U6xHq21orK+MsExGa44+nAzRxrqAAa30e9KnQy1PmQA5Zyev3CQXdrpo6lh2Plzd c1kPyUR7I0XLq18OQEKSnBpT8k0dTfdbQ/fs+lqdTYfct2z15RIwLJePCaXcno2a 1OVPbK9cC12taEbQ9M/O1qzZaUYrPieUEqkjhOi/sCnUfU6W3ixbvPTYt+D98hOT KyoQ90qp1ht3CWx9MveJfVFy8Nqb0SnfDQVj6WDMy0yLLaJHqT2RoPpnLqrQrEhx LqGlK4+nTTUMCEr7+vuLQKeog7TcA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrtdefgdduvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 D4CD380060; Wed, 11 Sep 2019 16:27:48 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dpdk-dev , John McNamara , Qian Xu Date: Wed, 11 Sep 2019 22:27:46 +0200 Message-ID: <3344692.kQovRPT8Ie@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 20.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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.