From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] Stable Tree coming to life
Date: Mon, 26 Sep 2016 20:09:49 +0800 [thread overview]
Message-ID: <20160926120949.GC20278@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <CAATJJ0Jr+6=a-dZtGnEmmbTg4rZkqKgU_6nejDR8xfMQeEmW3g@mail.gmail.com>
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
next prev parent reply other threads:[~2016-09-26 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 9:16 Christian Ehrhardt
2016-09-26 12:09 ` Yuanhan Liu [this message]
2016-09-26 13:27 ` Christian Ehrhardt
2016-09-26 13:40 ` Yuanhan Liu
2016-09-27 9:05 ` Mcnamara, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160926120949.GC20278@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).