From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com
 [209.85.212.169]) by dpdk.org (Postfix) with ESMTP id 50A609372
 for <dev@dpdk.org>; Wed, 21 Oct 2015 11:04:46 +0200 (CEST)
Received: by wicfv8 with SMTP id fv8so64789140wic.0
 for <dev@dpdk.org>; Wed, 21 Oct 2015 02:04:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=kjMRonOtRECUvosXl0LsRQfvVTjvUexMLeynbVKc9j4=;
 b=cQmCXntzAdQYirpX3W8o2Ok0Fc6fMFKIbfXHrPsd6qjP5phq4xbagHLA2XoUgzcHwR
 IJFyUdofzeQOoyEuK5GRacdSIelJnU/m53f63nPM109x8Tq5IJ5yB49OZaY/ye0i//dO
 h3348cb8wBSUimzFvO5kTYONRwgYLnqWrdzhZZMbrI443H/XQ1XbEmRdtrHSzcpsPqj/
 ioP+YVrYJzJPns0uNL2lUAfVlKoGSDkdpA+//bi8Bdg7FYRkTaUVwKWqPHTkPe7MSnDx
 ksJYJTCt3YkcC7eHt0a2ZigyAypo3dK5cGQF9FRK4SOd+AOK4meLMJPO3qNhm6ksdxqH
 ElCw==
X-Gm-Message-State: ALoCoQlK8sD4XpQU/NsFieJ8NgznO1jqqIVAwoY7mWE3ilBhBn/9b6s8g7MaVQyYgZ94P/AHklbh
X-Received: by 10.180.91.70 with SMTP id cc6mr10155824wib.58.1445418286030;
 Wed, 21 Oct 2015 02:04:46 -0700 (PDT)
Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net.
 [82.239.227.177])
 by smtp.gmail.com with ESMTPSA id bd4sm9031601wjb.15.2015.10.21.02.04.45
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 21 Oct 2015 02:04:45 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Panu Matilainen <pmatilai@redhat.com>
Date: Wed, 21 Oct 2015 11:03:41 +0200
Message-ID: <2265365.ZSeGOJNMlR@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <5627514D.1010103@redhat.com>
References: <20151015144406.1aaca698@xeon-e3> <2717598.bIV87FGGpb@xps13>
 <5627514D.1010103@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK patch backlog
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: Wed, 21 Oct 2015 09:04:46 -0000

2015-10-21 11:48, Panu Matilainen:
> On 10/21/2015 11:25 AM, Thomas Monjalon wrote:
> > 2015-10-20 21:34, Stephen Hemminger:
> >> Patch backlog is not getting better, now at 486.
> >>
> >> How can we break this logjam?
> >> Do I need to make a new "ready for merge" tree?
> >
> > What would mean "ready for merge"?
> > A lot of patches are acked but do not compile or doc is missing.
> 
> Well, isn't that one quite reasonable definition of being "ready"?
> - patch must be acked
> - patch must apply and compile (when relevant)
> - is appropriately documented (commit message style and all)

Yes.
Compilation must be tested with GCC and clang, as static and shared libraries
and for 32-bit and 64-bit targets.
Documented means good commit message and doc or release notes updated.