From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id EB4DD7E7A for ; Tue, 21 Oct 2014 10:14:09 +0200 (CEST) Received: from [192.168.1.43] (42.Red-79-146-253.dynamicIP.rima-tde.net [79.146.253.42]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id 7294EA2DA9 for ; Tue, 21 Oct 2014 10:22:24 +0200 (CEST) Message-ID: <544617E0.80502@bisdn.de> Date: Tue, 21 Oct 2014 10:22:56 +0200 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: "" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] development/integration branch? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Oct 2014 08:14:10 -0000 Good morning, Some DPDK users, including myself, use a clone of the git repository to compile DPDK for their applications, instead of downloading the tarball of each release. In my opinion, it would be useful for such users that the master branch contains only stable releases, to prevent (mistakenly) to use a wip DPDK version, and jump quickly to the latest stable with a simple git pull without having to check the tags. Also new users would clone the repo and get only the stable release. So I would propose to use an integration/development branch, where the patches are integrated and only push to master once a stable release is tagged in this integration branch. Thoughts? best marc