From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Liu, Yuanhan" <yuanhan.liu@intel.com>
Subject: Re: [dpdk-stable] Stable Tree coming to life
Date: Tue, 27 Sep 2016 09:05:55 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026246A1@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAATJJ0Jr+6=a-dZtGnEmmbTg4rZkqKgU_6nejDR8xfMQeEmW3g@mail.gmail.com>
> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Christian
> Ehrhardt
> Sent: Monday, September 26, 2016 10:16 AM
> To: stable@dpdk.org
> Subject: [dpdk-stable] Stable Tree coming to life
>
> Hi,
> first of all thank you all so much. It is great to see the stable tree
> finally getting patches.
>
> 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.
Hi,
The latest draft of the Stable/LTS doc is here:
http://dpdk.org/ml/archives/dev/2016-July/044848.html
>
> 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?
The parts about Testing and Releasing are reproduced here:
Testing
-------
Stable and LTS releases should be tested before release/tagging.
Intel will provide validation engineers to test the 16.07 Stable Release and
the initial LTS tree. Other community members should provide testing for other
stable releases.
The validation will consist of compilation testing on the range of OSes
supported by the master release and functional/performance testing on the
current major/LTS release of the following OSes:
* Ubuntu
* RHEL
* SuSE
* FreeBSD
Releasing
---------
A Stable Release will be released by:
* Tagging the release with YY.MM.nn (year, month, number) or similar.
* Uploading a tarball of the release to dpdk.org.
* Sending an announcement to the <announce at dpdk.org> list.
prev parent reply other threads:[~2016-09-27 9:06 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
2016-09-27 9:05 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2026246A1@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@dpdk.org \
--cc=yuanhan.liu@intel.com \
/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).