From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186])
 by dpdk.org (Postfix) with ESMTP id CA89658F7
 for <dev@dpdk.org>; Fri, 16 Jan 2015 23:45:50 +0100 (CET)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id 53C9580C79B; Fri, 16 Jan 2015 14:43:26 -0800 (PST)
Date: Fri, 16 Jan 2015 14:43:26 -0800
From: Matthew Hall <mhall@mhcomputing.net>
To: Neil Horman <nhorman@tuxdriver.com>
Message-ID: <20150116224326.GA1080@mhcomputing.net>
References: <20150114122352.63ef79eb@urahara> <2507392.XzU56ErIKp@xps13>
 <20150116172017.GE27496@hmsreliant.think-freely.org>
 <2188823.ZBC1oOX6oS@xps13> <20150116185852.GA29426@mhcomputing.net>
 <20150116200057.GG27496@hmsreliant.think-freely.org>
 <20150116203848.GA31715@mhcomputing.net>
 <20150116211438.GA22909@hmsreliant.think-freely.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150116211438.GA22909@hmsreliant.think-freely.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 22:45:51 -0000

On Fri, Jan 16, 2015 at 04:14:38PM -0500, Neil Horman wrote:
> Sure, Its a bit orthogonal to this conversation, but I think its a fine idea to
> have if it aids in general reviewing.  Thomas can it be setup on dpdk.org?
> 
> Neil

Admittedly I'm not a PMD expert to comment on all the specifics of what you 
said about subtrees. But I do like to think out of the box and look at the big 
picture of what people have to say in the various threads. Your points about 
making the community strong seemed important, so I thought about the various 
subproblems to solve the whole topic:

1) some logical subtrees as you advised,

2) a clarification of who runs the subtrees and who does the -next mergeups,

3) feature branches or some other way for end users to validate new related 
functionality all together as a kind of integration testing,

4) a MAINTAINERS file, and maybe a TESTERS file, or tester / end-user entries 
in MAINTAINERS,

5) a really good friend way to review the new code like Gerrit as you advised

I think if we attack all of these we should be in good shape as the community 
continues to grow and mature.

Matthew.