From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [dpdk-web] [PATCH v2] update stable releases roadmap Date: Wed, 18 Apr 2018 10:05:38 +0100 Message-ID: <776b230f-215a-8fec-1f2f-0b19064ba004@intel.com> References: <20180309133612.19927-1-thomas@monjalon.net> <20180410232813.2534-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, techboard@dpdk.org, bluca@debian.org, yliu@fridaylinux.org, ktraynor@redhat.com, christian.ehrhardt@canonical.com, yskoh@mellanox.com To: Thomas Monjalon , web@dpdk.org Return-path: In-Reply-To: <20180410232813.2534-1-thomas@monjalon.net> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 4/11/2018 12:28 AM, Thomas Monjalon wrote: > -

Typically a new stable release version follows a mainline release > - by 1-2 weeks, depending on the test results. > +

The first stable release (.1) of a branch should follow > + its mainline release (.0) by at least two months, > + after the first release candidate (-rc1) of the next branch. Hi Thomas, What this change suggest? To be able to backport patches from rc1?