From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by dpdk.org (Postfix) with ESMTP id 5ED6A7E2F for ; Fri, 26 Sep 2014 12:35:21 +0200 (CEST) Received: by mail-we0-f176.google.com with SMTP id w61so8501979wes.21 for ; Fri, 26 Sep 2014 03:41:43 -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=MY7oTCxCOUuBnLuJzCub0tOvsmlJhZvq0uOYtHTOPlU=; b=Mod6lWCKzbvf70NBnXrGJvp5ltsvDhJ998lPIxQAO7Si8lQobpWhv24wXVgG/WhPWz AvF02KLN2nq+gjibi3JFm87kkVnDvDcp8BZkNk5wguwQ9sVnpWMs6q4eOpRiYUdVL66m CeN57SEy6toIX0up3kCC+AI0YW/gsfsg2MSAg83mThFmDjx7nitYXOkWJg+mlA/xy0ri Z2h+Ameb819/CeRlLDyL6cKy0Kt5S0g8iEs8eRGmiQVp7LbSAkooilgq0dS0R0s3w1xc kZl2x+VYkDTeGa7RE4GVVa2YvhIz58VN6aDAuKGlhgpMY4QF3nXN3umYMFPjL8TzNCFN IVVg== X-Gm-Message-State: ALoCoQl7OU0wO7oYpU+fA8NkNco0WD8y2McrLhgq6uqmvxb8eIt10eN6fslgj2cMxdgW6AUBfQi3 X-Received: by 10.180.187.144 with SMTP id fs16mr44651241wic.75.1411728103143; Fri, 26 Sep 2014 03:41:43 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id ew1sm5670082wjb.31.2014.09.26.03.41.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Sep 2014 03:41:42 -0700 (PDT) From: Thomas Monjalon To: Neil Horman Date: Fri, 26 Sep 2014 12:41:33 +0200 Message-ID: <1449997.vdXo3dW1jx@xps13> Organization: 6WIND User-Agent: KMail/4.13.3 (Linux/3.15.8-1-ARCH; KDE/4.13.3; x86_64; ; ) In-Reply-To: <20140924181940.GB4651@hmsreliant.think-freely.org> References: <1410809031-19114-1-git-send-email-nhorman@tuxdriver.com> <20140918191401.GP20389@hmsreliant.think-freely.org> <20140924181940.GB4651@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 0/4] Add DSO symbol versioning to support backwards compatibility 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: Fri, 26 Sep 2014 10:35:21 -0000 Hi Neil, 2014-09-24 14:19, Neil Horman: > Ping Thomas. I know you're busy, but I would like this to not fall off anyones > radar. You alluded to concerns regarding what, for lack of a better term, > ABI/API lockin. I had asked you to enuumerate/elaborate on specifics, but never > heard back. Are there further specifics you wish to discuss, or are you > satisfied with the above answers? Sorry for not being very reactive on this thread. All this discussion is very interesting but it's really not the proper time to apply it. As you said, it requires an extra effort. I'm not saying it will never be integrated. I'm just saying that we cannot change everything at the same time. Let me sum up the situation. This community project has been very active for few months now. First, we learnt how to make some releases together and we are improving the process to be able to deliver a new major release every 4 months while having some good quality process. But these releases are still not complete because documentation is not integrated yet. Then developers should have a role in documentation updates. We also need to integrate and learn how to use more tools to be more efficient and improve quality. So the question is "when should we care about API compatibility"? And the answer is: ASAP, but not now. I feel next year is a better target. Because the most important priority is to move together at a pace which allow most of us to stay in the race. -- Thomas