Re: [dpdk-dev] Proposal for a new Committer model

2016-12-02 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Mcnamara, John > Sent: Wednesday, November 30, 2016 9:59 AM > To: Neil Horman > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] Proposal for a new Committer model > > > -Original

[dpdk-dev] Proposal for a new Committer model

2016-11-30 Thread Mcnamara, John
> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Tuesday, November 29, 2016 7:12 PM > To: Mcnamara, John > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] Proposal for a new Committer model > > > ... > > > > B) Desig

[dpdk-dev] Proposal for a new Committer model

2016-11-29 Thread Neil Horman
On Fri, Nov 18, 2016 at 01:09:35PM -0500, Neil Horman wrote: > On Thu, Nov 17, 2016 at 09:20:50AM +, Mcnamara, John wrote: > > Repost from the moving at dpdk.org mailing list to get a wider audience. > > Original thread: > > http://dpdk.org/ml/archives/moving/2016-November/59.html > > > >

[dpdk-dev] Proposal for a new Committer model

2016-11-25 Thread Neil Horman
On Thu, Nov 24, 2016 at 01:53:55PM +0800, Yuanhan Liu wrote: > On Wed, Nov 23, 2016 at 03:19:19PM -0500, Neil Horman wrote: > > On Wed, Nov 23, 2016 at 11:41:20PM +0800, Yuanhan Liu wrote: > > > On Wed, Nov 23, 2016 at 09:11:54AM -0500, Neil Horman wrote: > > > > > Could we define some of the poten

[dpdk-dev] Proposal for a new Committer model

2016-11-25 Thread Neil Horman
On Thu, Nov 24, 2016 at 10:17:09AM +0100, Thomas Monjalon wrote: > 2016-11-23 15:13, Neil Horman: > > Can either you or thomas provide some detail as to how you are doing patch > > management between trees (details of the commands you use are what I would > > be > > interested in). It sounds to me

[dpdk-dev] Proposal for a new Committer model

2016-11-24 Thread Yuanhan Liu
On Wed, Nov 23, 2016 at 03:19:19PM -0500, Neil Horman wrote: > On Wed, Nov 23, 2016 at 11:41:20PM +0800, Yuanhan Liu wrote: > > On Wed, Nov 23, 2016 at 09:11:54AM -0500, Neil Horman wrote: > > > > Could we define some of the potential subtrees now and look to > > > > introduce them in the this rel

[dpdk-dev] Proposal for a new Committer model

2016-11-24 Thread Thomas Monjalon
2016-11-23 15:13, Neil Horman: > Can either you or thomas provide some detail as to how you are doing patch > management between trees (details of the commands you use are what I would be > interested in). It sounds to me like there may be some optimization to be made > here before we even make cha

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Yuanhan Liu
On Wed, Nov 23, 2016 at 09:11:54AM -0500, Neil Horman wrote: > > Could we define some of the potential subtrees now and look to introduce > > them in the this release cycle? EAL and the Core libs, as suggested by > > Thomas, seem like 2 obvious ones. > > > Sure, I'd suggest the following: I wou

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Ferruh Yigit
On 11/23/2016 3:33 PM, Neil Horman wrote: > On Wed, Nov 23, 2016 at 02:01:44PM +, Ferruh Yigit wrote: >> On 11/23/2016 1:48 PM, Neil Horman wrote: >>> On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: On 11/22/2016 7:52 PM, Neil Horman wrote: > On Mon, Nov 21, 2016 at 09:52

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Neil Horman
On Wed, Nov 23, 2016 at 11:41:20PM +0800, Yuanhan Liu wrote: > On Wed, Nov 23, 2016 at 09:11:54AM -0500, Neil Horman wrote: > > > Could we define some of the potential subtrees now and look to introduce > > > them in the this release cycle? EAL and the Core libs, as suggested by > > > Thomas, see

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Neil Horman
On Wed, Nov 23, 2016 at 04:21:00PM +, Ferruh Yigit wrote: > On 11/23/2016 3:33 PM, Neil Horman wrote: > > On Wed, Nov 23, 2016 at 02:01:44PM +, Ferruh Yigit wrote: > >> On 11/23/2016 1:48 PM, Neil Horman wrote: > >>> On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: > On 11

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Ferruh Yigit
On 11/23/2016 1:48 PM, Neil Horman wrote: > On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: >> On 11/22/2016 7:52 PM, Neil Horman wrote: >>> On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: 2016-11-18 13:09, Neil Horman: > A) Further promote subtree maintainer

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Neil Horman
On Wed, Nov 23, 2016 at 02:01:44PM +, Ferruh Yigit wrote: > On 11/23/2016 1:48 PM, Neil Horman wrote: > > On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: > >> On 11/22/2016 7:52 PM, Neil Horman wrote: > >>> On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: > 20

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Neil Horman
ra, John > > Subject: Re: [dpdk-dev] Proposal for a new Committer model > > > > On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: > > > 2016-11-18 13:09, Neil Horman: > > > > A) Further promote subtree maintainership. This was a conversa

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Neil Horman
On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: > On 11/22/2016 7:52 PM, Neil Horman wrote: > > On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: > >> 2016-11-18 13:09, Neil Horman: > >>> A) Further promote subtree maintainership. This was a conversation that I > >>> p

[dpdk-dev] Proposal for a new Committer model

2016-11-23 Thread Mcnamara, John
> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Tuesday, November 22, 2016 7:52 PM > To: Thomas Monjalon > Cc: dev at dpdk.org; Mcnamara, John > Subject: Re: [dpdk-dev] Proposal for a new Committer model > > On Mon, Nov 21,

[dpdk-dev] Proposal for a new Committer model

2016-11-22 Thread Ferruh Yigit
On 11/22/2016 7:52 PM, Neil Horman wrote: > On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: >> 2016-11-18 13:09, Neil Horman: >>> A) Further promote subtree maintainership. This was a conversation that I >>> proposed some time ago, but my proposed granularity was discarded in favo

[dpdk-dev] Proposal for a new Committer model

2016-11-22 Thread Neil Horman
On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: > 2016-11-18 13:09, Neil Horman: > > A) Further promote subtree maintainership. This was a conversation that I > > proposed some time ago, but my proposed granularity was discarded in favor > > of something that hasn't worked as well

[dpdk-dev] Proposal for a new Committer model

2016-11-21 Thread Thomas Monjalon
2016-11-18 13:09, Neil Horman: > A) Further promote subtree maintainership. This was a conversation that I > proposed some time ago, but my proposed granularity was discarded in favor > of something that hasn't worked as well (in my opinion). That is to say a > few driver pmds (i40e and fm10k com

[dpdk-dev] Proposal for a new Committer model

2016-11-19 Thread Stephen Hemminger
why aren't some patches as marked trivial and accepted right away. On Fri, Nov 18, 2016 at 11:06 AM, Jerin Jacob < jerin.jacob at caviumnetworks.com> wrote: > On Fri, Nov 18, 2016 at 01:09:35PM -0500, Neil Horman wrote: > > On Thu, Nov 17, 2016 at 09:20:50AM +, Mcnamara, John wrote: > > > Rep

[dpdk-dev] Proposal for a new Committer model

2016-11-19 Thread Jerin Jacob
On Fri, Nov 18, 2016 at 01:09:35PM -0500, Neil Horman wrote: > On Thu, Nov 17, 2016 at 09:20:50AM +, Mcnamara, John wrote: > > Repost from the moving at dpdk.org mailing list to get a wider audience. > > Original thread: > > http://dpdk.org/ml/archives/moving/2016-November/59.html > > > >

[dpdk-dev] Proposal for a new Committer model

2016-11-18 Thread Neil Horman
On Thu, Nov 17, 2016 at 09:20:50AM +, Mcnamara, John wrote: > Repost from the moving at dpdk.org mailing list to get a wider audience. > Original thread: http://dpdk.org/ml/archives/moving/2016-November/59.html > > > Hi, > > I'd like to propose a change to the DPDK committer model. Curre

[dpdk-dev] Proposal for a new Committer model

2016-11-17 Thread Matthew Hall
On Thu, Nov 17, 2016 at 09:20:50AM +, Mcnamara, John wrote: > One committer to master represents a single point of failure and at times can > be inefficient. I have a lot more issues because of slow or inconclusive review of patches than I do because of committers. Often times they just get

[dpdk-dev] Proposal for a new Committer model

2016-11-17 Thread Mcnamara, John
Repost from the moving at dpdk.org mailing list to get a wider audience. Original thread: http://dpdk.org/ml/archives/moving/2016-November/59.html Hi, I'd like to propose a change to the DPDK committer model. Currently we have one committer for the master branch of the DPDK project. One c