From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: [dpdk-announce] release candidate 17.02-rc3
Date: Fri, 10 Feb 2017 17:55:54 +0100
Message-ID: <2064988.WKpZIqTNWj@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
To: announce@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

A new DPDK release candidate is ready for testing:
	http://dpdk.org/browse/dpdk/tag/?id=v17.02-rc3

It is February 10th, the third RC is out, bringing a lot of fixes.
A new release must be available every three months, preferably
at the beginning of the month. It means it is time to close the 17.02.

The last step is to check the release notes and acknowledge the
deprecation notices, preparing the next release.

Please, let's target Tuesday 14th as the release date.
There is a lot of work planned for 17.05.