From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <luca.boccassi@gmail.com>
Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67])
 by dpdk.org (Postfix) with ESMTP id D4E9844C3
 for <stable@dpdk.org>; Sun,  3 Jun 2018 22:23:03 +0200 (CEST)
Received: by mail-wm0-f67.google.com with SMTP id j15-v6so10993992wme.0
 for <stable@dpdk.org>; Sun, 03 Jun 2018 13:23:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to
 :references:content-transfer-encoding:mime-version;
 bh=95+eQKkrz0CHjmj0zPKyCA0KPTiNh2oSFrsXPqAMfxA=;
 b=b/PSkgEaQ/X8bn5xEFqDx2b5tGBet6uW2Swe2b68hLeVpN33Ac1G6yEQuVLWqRA9oC
 utWvdIj0mI1gOtNERlFi5f6mts1YTTkLKKBvHxanygVMbtXSd++oJGJQMA9Wyvuk/kvK
 eEqfzQk6gfvfbnpLDmR7HUKqD3qcZhvLHEK+vw5gurX3j0eS2ibX46J4RhBoPlxrGwPo
 SmPswBf41haO6O8ZFHPxdhmBxRmJmxS6VHSvt7zW5JUXmpLj8gP7ZsIdaNVsgY9CPhDn
 W3PkSQZWTeNE7WTGQBHzr45UjKJAul2oppFzBIbhZSfJxB677bOwgA1pA6w5ohrf9nPi
 w4NA==
X-Gm-Message-State: APt69E1KUHkMcAiMv3wn3Uj8JI41T8wJ4ZPtMWuIGggNOmXp9tCDBd/9
 8qEmheKmG34NR3b9dJX9kMM=
X-Google-Smtp-Source: ADUXVKJnQv5aBmW81+jvS8LJtIlLT8YTnT4W+WMlKU/B5pjZEiyjZ1T0yCFhqrbnxpCtPJgJ6J2aiQ==
X-Received: by 2002:a1c:d681:: with SMTP id
 n123-v6mr3707834wmg.158.1528057383570; 
 Sun, 03 Jun 2018 13:23:03 -0700 (PDT)
Received: from localhost ([2a00:23c5:be9a:5200:44e7:1f9e:eb4:c6b6])
 by smtp.gmail.com with ESMTPSA id s5-v6sm49400086wra.48.2018.06.03.13.23.01
 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
 Sun, 03 Jun 2018 13:23:02 -0700 (PDT)
Message-ID: <1528057381.9772.3.camel@debian.org>
From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, Yuanhan Liu <yliu@fridaylinux.org>
Cc: Kevin Traynor <ktraynor@redhat.com>, Yongseok Koh <yskoh@mellanox.com>, 
 stable@dpdk.org
Date: Sun, 03 Jun 2018 21:23:01 +0100
In-Reply-To: <10687100.Bg4LDGQuS2@xps>
References: <20180527053517.lv24ma5n452na3cm@yuanhanliu-NB0.tencent.com>
 <3962613.dM9x5Q0JGJ@xps>
 <20180602051334.5vpjgalrfhlfjvk3@yuanhanliu-NB0.tencent.com>
 <10687100.Bg4LDGQuS2@xps>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Evolution 3.22.6-1+deb9u1 
Mime-Version: 1.0
Subject: Re: [dpdk-stable] 17.11.3 (LTS) patches review and test
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches for DPDK stable branches <stable.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/stable>,
 <mailto:stable-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/stable/>
List-Post: <mailto:stable@dpdk.org>
List-Help: <mailto:stable-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/stable>,
 <mailto:stable-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2018 20:23:04 -0000

On Sun, 2018-06-03 at 19:52 +0200, Thomas Monjalon wrote:
> 02/06/2018 07:13, Yuanhan Liu:
> > On Mon, May 28, 2018 at 12:30:01PM +0200, Thomas Monjalon wrote:
> > > About the process, I wonder what should be the reference branch
> > > when backporting.
> > > For example, could we use 18.02 stable branch to backport in
> > > 17.11?
> >=20
> > We normally do (and should) not do that. For fixes not from the
> > master
> > branch, the author should send a patch alone to the stable list,
> > telling
> > the maintainer this patch is stable only and should apply to stable
> > release X, Y, etc.
>=20
> Why we should not base branch n-2 on branch n-1?
> If a backport effort is done to port a patch from n to n-1,
> we could re-use that for n-2, instead of re-doing the same effort.

One problem is that it would add additional delay - rather than
preparing all stable releases at the same time, n-1 has to be done
first, then n-2, then n-3, etc

--=20
Kind regards,
Luca Boccassi