From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>,
john.mcnamara@intel.com, marko.kovacevic@intel.com,
dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: note validation and timeline required for stables
Date: Wed, 27 Mar 2019 17:25:47 +0000 [thread overview]
Message-ID: <65000618657f3eef2b1ba5f802ea59bc0ff81d5e.camel@debian.org> (raw)
Message-ID: <20190327172547.d-5GxysYaDqZf18vm0RHdoxmlJ91Af89gvCZFj75LrY@z> (raw)
In-Reply-To: <20190327172206.16187-1-ktraynor@redhat.com>
On Wed, 2019-03-27 at 17:22 +0000, Kevin Traynor wrote:
> If a stable branch for a specific DPDK release is to proceed,
> along with needing a maintainer, there should also be commitment
> from major contributors for validation of the releases.
>
> Also, as decided in the March 27th techboard, to facilitate user
> planning, a release should be designated as a stable release
> no later than 1 month after it's initial master release.
>
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
>
> v2: add 1 month deadline to designate as stable release.
> I didn't add v1 acks, as this is something new.
>
> doc/guides/contributing/stable.rst | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index 4214103b3..b63cd4228 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -27,5 +27,7 @@ Stable Releases
>
> Any major release of DPDK can be designated as a Stable Release if a
> -maintainer volunteers to maintain it.
> +maintainer volunteers to maintain it and there is a commitment from
> major
> +contributors to validate it before releases. If a release is to be
> designated
> +as a Stable Release, it should be done by 1 month after the master
> release.
>
> A Stable Release is used to backport fixes from an ``N`` release
> back to an
Acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-03-27 17:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 11:44 [dpdk-dev] [PATCH] doc: note validation commitment " Kevin Traynor
2019-03-22 11:44 ` Kevin Traynor
2019-03-22 13:30 ` Luca Boccassi
2019-03-22 13:30 ` Luca Boccassi
2019-03-25 10:14 ` Kovacevic, Marko
2019-03-25 10:14 ` Kovacevic, Marko
2019-03-27 17:22 ` [dpdk-dev] [PATCH v2] doc: note validation and timeline " Kevin Traynor
2019-03-27 17:22 ` Kevin Traynor
2019-03-27 17:25 ` Luca Boccassi [this message]
2019-03-27 17:25 ` Luca Boccassi
2019-04-05 13:36 ` Thomas Monjalon
2019-04-05 13:36 ` Thomas Monjalon
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=65000618657f3eef2b1ba5f802ea59bc0ff81d5e.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.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).