From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent JARDIN Subject: Re: releases scheduling Date: Tue, 15 Dec 2015 22:40:45 +0100 Message-ID: <567088DD.1070203@6wind.com> References: <1667533.heuKAiE6KB@xps13> <26FA93C7ED1EAA44AB77D62FBE1D27BA6747CE41@IRSMSX108.ger.corp.intel.com> <567066CF.2040404@redhat.com> <7C846718-93F5-46D4-BD1F-6D618C192973@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: "Wiles, Keith" Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 1870E569C for ; Tue, 15 Dec 2015 22:40:47 +0100 (CET) Received: by mail-wm0-f49.google.com with SMTP id l126so12812844wml.1 for ; Tue, 15 Dec 2015 13:40:47 -0800 (PST) In-Reply-To: <7C846718-93F5-46D4-BD1F-6D618C192973@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 15/12/2015 22:15, Wiles, Keith wrote: > I see the YY.MM.PP (PP is patch number) as the simplest way to keep track of when a release was done. +1 I like it.