From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id CE1147E7B for ; Wed, 22 Oct 2014 08:53:36 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id F102980C50B; Wed, 22 Oct 2014 00:00:58 -0700 (PDT) Date: Wed, 22 Oct 2014 00:00:58 -0700 From: Matthew Hall To: Thomas Monjalon , Marc Sune Message-ID: <20141022070058.GA6051@mhcomputing.net> References: <544617E0.80502@bisdn.de> <39275062.2hPoVIfNVy@xps13> <54462403.3060107@bisdn.de> <3074245.k7N1CrtUjD@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3074245.k7N1CrtUjD@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [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: Wed, 22 Oct 2014 06:53:37 -0000 On Tue, Oct 21, 2014 at 11:28:47AM +0200, Thomas Monjalon wrote: > But I care about the message brought by such change. It would mean that > we can break the development branch and that most of developers don't test > it nor base their patches on the latest commit. It's all about simple rules > and messages. I have seen two common ways to do this which I think are about equal. 1) master is latest release in production, develop branch is tip 2) master is tip, production releases live in branches / tags A lot of non-free stuff uses (1) along with some open source. So the DPDK is using model (2), which is pretty common for open source. What I think git in general and DPDK in particular are missing is, they have a tradition tags for releases, however I think this is broken because you can't easily append more stuff to tages. I really prefer putting my releases on actual branches to make it as easy as possible for users / maintenance programmers to follow and/or add stuff to a codeline. For example I'd like a 1.7.X branch I could follow for my app until 1.8.X is ready. Having a stable branch would also make stuff easier for guys like Marc who want to follow the known-stable release in an easy way without horsing around with "the latest tag of the day" all the time. Perhaps this is an OK option? Matthew.