From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [dpdk-web] [PATCH v2] update stable releases roadmap Date: Wed, 18 Apr 2018 11:14:26 +0200 Message-ID: <2746771.jHPYkc9GPR@xps> References: <20180309133612.19927-1-thomas@monjalon.net> <20180410232813.2534-1-thomas@monjalon.net> <776b230f-215a-8fec-1f2f-0b19064ba004@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: web@dpdk.org, dev@dpdk.org, techboard@dpdk.org, bluca@debian.org, yliu@fridaylinux.org, ktraynor@redhat.com, christian.ehrhardt@canonical.com, yskoh@mellanox.com To: Ferruh Yigit Return-path: In-Reply-To: <776b230f-215a-8fec-1f2f-0b19064ba004@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 18/04/2018 11:05, Ferruh Yigit: > 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? Yes, it is the proposal we discussed earlier. We can wait one week after RC1 to get some validation confirmation. Do you agree?