DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, orika@mellanox.com,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove major in designation of normal releases
Date: Thu, 13 Feb 2020 20:51:23 +0000	[thread overview]
Message-ID: <eea26f4f-a470-436b-1af2-4889f5fb7156@redhat.com> (raw)
In-Reply-To: <20190805123012.26581-1-thomas@monjalon.net>

On 05/08/2019 13:30, Thomas Monjalon wrote:
> The word "major" was used to differentiate with release candidates
> or stable maintenance releases.
> However the word "major" can be understood as "LTS",
> so it is less confusing to avoid this word.
> 
> Reported-by: Ori Kam <orika@mellanox.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  doc/guides/contributing/documentation.rst | 2 +-
>  doc/guides/contributing/stable.rst        | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/guides/contributing/documentation.rst b/doc/guides/contributing/documentation.rst
> index 27e4b13be..550d8dec2 100644
> --- a/doc/guides/contributing/documentation.rst
> +++ b/doc/guides/contributing/documentation.rst
> @@ -62,7 +62,7 @@ added to by the developer.
>  
>    The Release Notes document which features have been added in the current and previous releases of DPDK and highlight
>    any known issues.
> -  The Releases Notes also contain notifications of features that will change ABI compatibility in the next major release.
> +  The Releases Notes also contain notifications of features that will change ABI compatibility in the next release.
>  
>    Developers should include updates to the Release Notes with patch sets that relate to any of the following sections:
>  
> diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst
> index 6a5eee9bd..24b9e8b7d 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -25,7 +25,7 @@ Release to indicate longer term support.
>  Stable Releases
>  ---------------
>  
> -Any major release of DPDK can be designated as a Stable Release if a
> +Any release of DPDK can be designated as a Stable Release if a
>  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.
> 

Acked-by: Kevin Traynor <ktraynor@redhat.com>

(Prompted-by: David Marchand <david.marchand@redhat.com> ;-))


  reply	other threads:[~2020-02-13 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 12:30 Thomas Monjalon
2020-02-13 20:51 ` Kevin Traynor [this message]
2020-02-14  7:54 ` David Marchand

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=eea26f4f-a470-436b-1af2-4889f5fb7156@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=orika@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).