From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 8FE3F16E for ; Mon, 30 Apr 2018 15:02:40 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EE96B229C9; Mon, 30 Apr 2018 09:02:39 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 30 Apr 2018 09:02:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=+wyHMsFyompAfFPqjkqTDrjVCV oL9awKYNk0MCMi/Co=; b=ULs9vazcOYwIIFuYQe75IgO6lrS7aHBB79lE+KcY8/ jnfRoSCCwhmIitLN8m2zS6hKCtu3Fx1V0LvWWzNip0C3tD0i+JshrYTg/MNMTtDV 5+wObriRZrUReo/JKO829jKps1AZSw4oaErORnzQEA1lzgSvp+rIqmMXvpOymthY 8= 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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=+wyHMs FyompAfFPqjkqTDrjVCVoL9awKYNk0MCMi/Co=; b=BVp3ygVzxUm+c+o+4esipC A5+JmFl8QMRCrggSE6tUeFoJNKhxecijq5IvlVAuGlWCMAu1Rn64zoQgcNWXMGU7 WNj8XUAvQTkr4DEHhcemN5CN/vphX2cOP0iN7Rhn5tPJp1PAoxEAGPaRTIztSmzY x0ZJ9uDseK14kk8419vBdtP80jkMHfS2RXVUigHIS99PBft95S96GfKgw+0QuIX/ s+sc6/KxQ9gv2SZgyualkzH8S/qKgSdCErUCdxlJSvCfoil6CAXUg71ShF6KZ+t3 kHKe4u7yGazMbYuNovJiXeAyz1N8QBvEVPeMnc8qYShsxmnssBE+sfETWpsfwnVQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 51401E4F05; Mon, 30 Apr 2018 09:02:39 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: dev@dpdk.org, ferruh.yigit@intel.com Date: Mon, 30 Apr 2018 15:02:38 +0200 Message-ID: <4994002.UncbAHUyZt@xps> In-Reply-To: <20180430125743.GC100464@bricha3-MOBL.ger.corp.intel.com> References: <20180430125743.GC100464@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] New RC needed for stablility? 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: Mon, 30 Apr 2018 13:02:40 -0000 30/04/2018 14:57, Bruce Richardson: > Hi Thomas, Ferruh, all, > > Initial testing on RC1 from our System Test and Validation shows a lot of > defects/issues, and from the list it appears others may be seeing issues > too. These issues, as well as causing test failures are blocking other > tests from being run. We are also seeing some serious performance > regressions with testpmd. > > Based on the number of issues we are seeing, which is probably a result of > the huge number of changes in this release even at the RC1 point, I would > propose that we look to do a new RC some time this week to get as many > critical bugs as possible ironed out, before we add in the remaining 18.05 > features. That is: *bug-fix only* RC2, say Wed/Thurs (or sooner if fixes > are ready), with remaining features in RC3 as planned on 11th. > > Thoughts, comments? OK +1 We need to agree on a list of bugs to be fixed. Are there some Bugzilla entries? When they will be fixed, I will tag the RC2.