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 21:40:47 +0800 [thread overview]
Message-ID: <20160926134047.GI20278@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <CAATJJ0Jje1F6OGWMfsTAspQ8AyCvASASVsTMzhPd4YSoZ04xnw@mail.gmail.com>
On Mon, Sep 26, 2016 at 03:27:41PM +0200, Christian Ehrhardt wrote:
>
> On Mon, Sep 26, 2016 at 2:09 PM, Yuanhan Liu <yuanhan.liu@linux.intel.com>
> wrote:
>
> Following is something you want to know? (the "About releases" section)
>
> http://dpdk.org/ml/archives/dev/2016-September/046189.html
>
>
> Thanks that was what I was looking for!
Good to know.
> [...]
>
>
> 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.
>
> ...
>
> 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.
>
>
> Sure, I'd try to pass it through some tests as hopefully others will do as
> well.
> 1 week prior to release is a bit short maybe, if that could be two that would
> be great.
Granted :) -- well, if others have no objection.
--yliu
> I don't mind the list being not 100% complete at that time, it is more about
> realizing
> "o yeah there is coming something I might need to prep the testbed and allocate
> some time"
>
>
>
> --
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd
next prev parent reply other threads:[~2016-09-26 13:40 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
2016-09-26 13:27 ` Christian Ehrhardt
2016-09-26 13:40 ` Yuanhan Liu [this message]
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=20160926134047.GI20278@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).