From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D48A422545; Fri, 29 Jun 2018 18:02:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 29 Jun 2018 18:02:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=wzBcg314QTNBj1vlR2Vz6nHJjk bXGY9bSmdmR6CPJJ0=; b=mebgM4wJzUPtp6zpoiur3VO25YOybbM6a9KhyhBOd/ WrQis6TK6WS3guUYKT50D/5MCqHxjatFZuWOHa/XGjhQwA1ZhcqhtI9npUdLoRiK CilOFmespXJk6kaNYZJEKb13ZgpNGx8ioPx8XSF7f2VFqZF/14pRKL8X4yGGUxuU Y= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=wzBcg3 14QTNBj1vlR2Vz6nHJjkbXGY9bSmdmR6CPJJ0=; b=NEul+ibmxJTwPDFQcLNQDf x7iZjBeLjt5grLvIx/go90FRTq2vmseSmFyFoETQR4bOLaqszvfpdfXBeKUL9qA4 DljNvnhLPGTNtc+Q6Hk+QrrnR0MDUw2wR8l2F84gDY1PswQuaP9zgxpwzh5fGAdE H9GBIPrtIP9eIdoE/UJZQGbF14QckYt2M3Z2d2rEltQCng6cby2OHuYEiXGGh0IM +cyw47U26EaYDFbeiY9GkO+HpsQQ/BGftQv4UQoloTgUWelEHdiMUYrUwH8Q1AQi 3378tZdSL8KlZSKymarlGWq7MhZqGMOTjGhK7v4+UfO4bUE49rPapTXnyM3q8PlA == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 09A631025C; Fri, 29 Jun 2018 18:02:15 -0400 (EDT) From: Thomas Monjalon To: Kevin Traynor 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 Date: Sat, 30 Jun 2018 00:02:14 +0200 Message-ID: <9109842.NZQjWO3Re5@xps> In-Reply-To: <1530308851-30496-1-git-send-email-ktraynor@redhat.com> References: <1529596827-14756-1-git-send-email-ktraynor@redhat.com> <1530308851-30496-1-git-send-email-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] docs: add default that all fixes should be backported X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 22:02:18 -0000 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