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 15:28:44 +0200 Message-ID: <2289123.B0I2yLRMB9@xps> References: <20180309133612.19927-1-thomas@monjalon.net> <2746771.jHPYkc9GPR@xps> 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: 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 14:28, Ferruh Yigit: > On 4/18/2018 10:14 AM, Thomas Monjalon wrote: > > 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? > > This has been discussed in tech-board, what I remember the decision was to wait > the release to backport patches into stable tree. It was not so clear to me. I thought post-rc1 was acceptable. The idea is to speed-up stable releases pace, especially first release of a series.