From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id AA3814CB5; Mon, 28 Jan 2019 03:10:08 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 778BF4CA6 for ; Mon, 28 Jan 2019 03:10:07 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0A07121E8D; Sun, 27 Jan 2019 21:10:07 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 27 Jan 2019 21:10:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=mesmtp; bh=ox6ar7jI7D 6c6sqN3X+w+IHw9HRLzrP4Qrhfb+TcfYE=; b=KocNi/s8/GE5V7Qb8zfP+dyYai QZdb8qCe+33vumA99oorjJTrvPKQGqYXOCTeg9z5r38wtFnOg0lgX1B27h+5gFoH r5YfvT9sX+76XvZU+ATX9zJ+lFD/ZHEWVBnRtQNEdU8FWMlavf/NbPmYUgosIzqX SuHtOoiX7YuD/svz4= 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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ox6ar7 jI7D6c6sqN3X+w+IHw9HRLzrP4Qrhfb+TcfYE=; b=GurEsb0PnJEzqK9BLKQKTI +WQcDT4BIDh0ilkfbpgYtpLVcBpEEBRGBHpKp8SFKp79Y3/pTqOdI/o533VqOLmY RB97A013z6NzFb6drkoir3FLbsMKqRzCsVybDmQKjlFxxDtpF2nR2B+sAkfR58n7 5kcOhe9GlHuuMdRbm5YVCMpfqM7AyR6/mwbOcYgwJD7UMB+E4J/wtOX8pOFd6i64 VKTKetEJMCMvP0VfR1VGG69FT9qp+sAR6DZv+PpuOOHhVat1jnLY4KCx0WrIwTMh Y2cqkLeOJ6ZDl+rz0S82lwKIg9tydfhpANayRFs/IkW8BmocLeEPCXKJwmSGqvuQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrieelgdeghecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucenucfjughrpefhvffufffkggfgtgesthfuredttddtvdenucfhrhhomhepvfhhoh hmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeen ucffohhmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvddtfedrudekge enucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgv thenucevlhhushhtvghrufhiiigvpedt 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 63861E4124 for ; Sun, 27 Jan 2019 21:10:06 -0500 (EST) From: Thomas Monjalon To: announce@dpdk.org Date: Mon, 28 Jan 2019 03:10:05 +0100 Message-ID: <13983341.c6sE5FLPCF@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Errors-To: announce-bounces@dpdk.org Sender: "announce" Subject: [dpdk-dev] [dpdk-announce] release candidate 19.02-rc4 X-BeenThere: dev@dpdk.org List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 02:10:08 -0000 A new DPDK release candidate is ready for testing: https://git.dpdk.org/dpdk/tag/?id=v19.02-rc4 The release notes: http://doc.dpdk.org/guides/rel_notes/release_19_02.html 42 patches (docs and fixes) were integrated. This is the last release candidate for DPDK 19.02. You may share some release validation results by replying to this message (at dev@dpdk.org). If no objection, the version 19.02.0 will be out on February 1st. If you are preparing the next release cycle, please send your v1 patches before the 19.05 proposal deadline, which will happen on March 1st. PS: *CfP for India summit of March 9th is closing today!* https://www.dpdk.org/event/dpdk-summit-bangalore-2019/