From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id BC1327E7B for ; Tue, 21 Oct 2014 10:29:53 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 21 Oct 2014 01:38:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="403409111" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by FMSMGA003.fm.intel.com with ESMTP; 21 Oct 2014 01:30:31 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.175]) by IRSMSX102.ger.corp.intel.com ([169.254.2.200]) with mapi id 14.03.0195.001; Tue, 21 Oct 2014 09:36:13 +0100 From: "Richardson, Bruce" To: Marc Sune , "" Thread-Topic: [dpdk-dev] development/integration branch? Thread-Index: AQHP7QhdRvh90qypL0qE81L/tU8Z/pw6OIiw Date: Tue, 21 Oct 2014 08:36:13 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B0344210F9@IRSMSX103.ger.corp.intel.com> References: <544617E0.80502@bisdn.de> In-Reply-To: <544617E0.80502@bisdn.de> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Tue, 21 Oct 2014 08:29:54 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marc Sune > Sent: Tuesday, October 21, 2014 9:23 AM > To: > Subject: [dpdk-dev] development/integration branch? >=20 > Good morning, >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Thoughts? >=20 > best > marc Ideally, our master branch should always be good and stable, but given real= ity often interferes with such good intentions I think that having dev bran= ches is not a bad idea. However, what we may lose by doing so is having a l= arger group of people constantly using the master branch and reporting prob= lems to us.=20 On balance, I'd be slightly in favour of this suggestion. /Bruce