From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] docs: add default that all fixes should be backported Date: Sat, 30 Jun 2018 00:02:14 +0200 Message-ID: <9109842.NZQjWO3Re5@xps> References: <1529596827-14756-1-git-send-email-ktraynor@redhat.com> <1530308851-30496-1-git-send-email-ktraynor@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: john.mcnamara@intel.com, bluca@debian.org, yskoh@mellanox.com, christian.ehrhardt@canonical.com, dev@dpdk.org, aconole@redhat.com, ferruh.yigit@intel.com To: Kevin Traynor Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 5FEF01B6A1 for ; Sat, 30 Jun 2018 00:02:18 +0200 (CEST) In-Reply-To: <1530308851-30496-1-git-send-email-ktraynor@redhat.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" 29/06/2018 23:47, Kevin Traynor: > -Backporting should be limited to bug fixes. > +Backporting should be limited to bug fixes. All patches accepted on the master > +branch with Fixes tags 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. > > Features should not be backported to stable releases. It may be acceptable, in > @@ -77,5 +80,6 @@ list. > All fix patches to the master branch that are candidates for backporting > should also be CCed to the `stable@dpdk.org `_ > -mailing list. > +mailing list. Absence of this CC is an indication that the patch is not suitable > +for backporting. We should mention that it is not a matter of Cc'ing the dpdk-stable ML, but more importantly, a tag which remains in the git history: Cc: stable@dpdk.org