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 13:28:00 +0100 Message-ID: References: <20180309133612.19927-1-thomas@monjalon.net> <20180410232813.2534-1-thomas@monjalon.net> <776b230f-215a-8fec-1f2f-0b19064ba004@intel.com> <2746771.jHPYkc9GPR@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 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: Thomas Monjalon Return-path: In-Reply-To: <2746771.jHPYkc9GPR@xps> 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/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.