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 8D3BD5588 for ; Mon, 26 Sep 2016 14:09:24 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 26 Sep 2016 05:09:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,399,1470726000"; d="scan'208";a="1062384231" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga002.fm.intel.com with ESMTP; 26 Sep 2016 05:09:19 -0700 Date: Mon, 26 Sep 2016 20:09:49 +0800 From: Yuanhan Liu To: Christian Ehrhardt Cc: stable@dpdk.org Message-ID: <20160926120949.GC20278@yliu-dev.sh.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-stable] Stable Tree coming to life X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 12:09:25 -0000 On Mon, Sep 26, 2016 at 11:16:26AM +0200, Christian Ehrhardt wrote: > Hi, > first of all thank you all so much. It is great to see the stable tree > finally getting patches. Right, sorry for that: I should have done that a bit earlier. It's the first trial, it took a bit time to think about what could be a more proper way to do it. > I wanted to clarify one thing though. I know it was discussed initially but > I haven't found the consensus and it didn't get to a doc file that I'd have > found either. > > Will the stable tree just hold a continues series of fixes on top of DPDK > (16.07 in the current case)? > Or will there be "releases" of the stable tree which are considered more > tested? > Like releasing 16.07.1 along 16.11 or such? Following is something you want to know? (the "About releases" section) http://dpdk.org/ml/archives/dev/2016-September/046189.html About testing, short answer: no dedicated test plan *yet*. But judging that I just pick patches from master branch, and the validation team here does testing for each release. That would somehow implies the quality a bit. Meanwhile, I will try to ask if the validation could provide some dedicated testing help. They're willing to offer help before. Last, it'd also be great if distributions like canonical could do some tests. The validation team here, for sure, can't cover all cases; otherwise, there would be no reason for stable release. We could make it more solid with more testing from more people. And (likely one week) before each stable release, I will send the applied patch list out, for asking more reviews as well as tests. After that, I will make a release. Am I missing something? --yliu > > In case I just lost too much grip of the old thread feel free to just pass > me a ML link in which part it was defined. > > Kind Regards, > > -- > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd