From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id D81462583 for <announce@dpdk.org>; Wed, 2 May 2018 23:48:59 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 633BA20C59; Wed, 2 May 2018 17:48:59 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 02 May 2018 17:48:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=qypE09x8kLAKunoMxiiFinuHy26XMveuYC2dlvwyK4M=; b=dyo5U iYMMG+fxLLoXCID3Z2wrgkXk7oHHgTGXAtjoZW9UfEbb5hmYd8bS5jvXEtUKuSbT ZLamoQGp72QOAvymrtu+VfnIqy1U8hGbthu40of1xBRNGLd+KzA3Hgsn0Di0MZ/D mc8m9GhjXlL/XtDRiHCXr86C9we//r/z6l1yjE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=qypE09x8kLAKunoMxiiFinuHy26XM veuYC2dlvwyK4M=; b=ltuFpAMO/hm8afDPKv9ozym8A+MBRE7FwK1ca/gcfQCKG V28WBbOX94vzjANJ7/C+x7wYfiKqkbt5hANziLQ5z8eudTPfAKM1b7DJrEaPyGHH x/NjKNE+cfWQzvLa3jJL4VtPNoL06pmWD6056c95KkjmrUtAiNhAOm43626QFe9H w/JQs4nRvgIhYRfK4g0lVRZv6S3ClBEDffd2Bs8qpEvc/jxtLKpsnXvpSelz9hxa nifCiMaqNlQbP+QbNNlzY6fF3DgshkqzrIKR+8RQxPZI5fJ9i53wWF9MQNRAvwUW K0w+ab9A+EkgDZ/wbtoc1SauYJERX80xGUln7LRYg== X-ME-Sender: <xms:SzLqWsszHbIIgWR6ZnMig8nLi07btnBHZptUNOs4-8zUV7yRXO0yAQ> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CF192E5036 for <announce@dpdk.org>; Wed, 2 May 2018 17:48:58 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: announce@dpdk.org Date: Wed, 02 May 2018 23:48:57 +0200 Message-ID: <35498312.SIduyevxMj@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-announce] release candidate 18.05-rc2 X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK announcements <announce.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/announce>, <mailto:announce-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/announce/> List-Post: <mailto:announce@dpdk.org> List-Help: <mailto:announce-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/announce>, <mailto:announce-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 02 May 2018 21:49:00 -0000 A new DPDK release candidate is ready for testing: https://dpdk.org/browse/dpdk/tag/?id=v18.05-rc2 The release notes are not updated in this RC2: http://dpdk.org/doc/guides/rel_notes/release_18_05.html None of the features planned for RC2 is merged. It is a release candidate to fix only the major bugs seen in RC1. It will allow to better progress with 18.05 validation tests. Major bugs fixed: - deadlock or crash in control thread initialization - deadlock in memory initialization - race condition when freeing - strong RSS configuration expectation - buggy atomic exchange on i686 As a consequence, the plan previously announced for RC2 is kept and renamed as the RC3 plan: see http://dpdk.org/ml/archives/announce/2018-April/000193.html Hope this release candidate will be better for testing, and that we can have a feature complete RC3 by the end of the next week, i.e. Friday 11th.