From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3] docs: add default that all fixes should be backported Date: Wed, 11 Jul 2018 23:04:19 +0200 Message-ID: <1931851.rl9UeLAVdt@xps> References: <1530308851-30496-1-git-send-email-ktraynor@redhat.com> <1530313843-32721-1-git-send-email-ktraynor@redhat.com> <4890282.64px6iNzis@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, john.mcnamara@intel.com, bluca@debian.org, yskoh@mellanox.com, christian.ehrhardt@canonical.com, aconole@redhat.com, ferruh.yigit@intel.com To: Kevin Traynor Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id C5AD01B50F for ; Wed, 11 Jul 2018 23:04:24 +0200 (CEST) In-Reply-To: <4890282.64px6iNzis@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 04/07/2018 17:22, Thomas Monjalon: > 30/06/2018 01:10, Kevin Traynor: > > Set the starting point that all commits on master branch > > with Fixes tag should be backported to relevant stable/LTS > > branches, and explain that the submitter may indicate it is > > not suitable for backport. > > > > Of course there will be exceptions that will crop up from time > > to time that need discussion, so also add a sentence for that. > > > > This is to ensure that there is consistency between what is > > backported to stable/LTS branches, remove some subjectivity > > as to what constitutes "a fix" and avoid possible conflicts > > for future backports. > > > > Signed-off-by: Kevin Traynor > > Acked-by: Luca Boccassi > > Acked-by: Aaron Conole > > --- > > -Backporting should be limited to bug fixes. > > +Backporting should be limited to bug fixes. All patches accepted on the master > > +branch with a Fixes: tag should be backported to the relevant stable/LTS > > +branches, unless the submitter indicates otherwise. If there are exceptions, > > +they will be discussed on the mailing lists. > > + > > +Fixes suitable for backport should have a ``Cc: stable@dpdk.org`` tag in the > > +commit message body as follows:: > > + > > + doc: fix some parameter description > > + > > + Update the docs, fixing description of some parameter. > > + > > + Fixes: abcdefgh1234 ("doc: add some parameter") > > + Cc: stable@dpdk.org > > + > > + Signed-off-by: Alex Smith > > + > > + > > +Fixes not suitable for backport should not include the ``Cc: stable@dpdk.org`` tag. > > Acked-by: Thomas Monjalon > > The technical board reviewed it and approve this clarified guideline. Applied, thanks