From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>, Neil Horman <nhorman@tuxdriver.com>,
Ray Kinsella <ray.kinsella@intel.com>
Subject: Re: [dpdk-dev] [PATCH] version: 20.02-rc0
Date: Mon, 2 Dec 2019 16:29:06 +0100 [thread overview]
Message-ID: <CAJFAV8zzOKrAQH1eT6Ce6LiNHBmDXseDnwDrZWh+Cpxa+E1ncw@mail.gmail.com> (raw)
In-Reply-To: <20191202145718.16407-1-thomas@monjalon.net>
On Mon, Dec 2, 2019 at 3:57 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> Start a new release cycle with empty release notes.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> ---
>
> I would prefer increasing the ABI version to 20.2
> for an easy mapping with code version:
> DPDK 19.11 = ABI 20
> libs 19.11 = .so.20.0
> DPDK 20.02 = ABI 20
> libs 20.02 = .so.20.2
> DPDK 20.05 = ABI 20
> libs 20.05 = .so.20.5
> DPDK 20.08 = ABI 20
> libs 20.08 = .so.20.8
>
> Opinions?
+1 but no strong opinion.
> ---
> ABI_VERSION | 2 +-
> VERSION | 2 +-
> doc/guides/rel_notes/index.rst | 1 +
> doc/guides/rel_notes/release_20_02.rst | 139 +++++++++++++++++++++++++
> 4 files changed, 142 insertions(+), 2 deletions(-)
> create mode 100644 doc/guides/rel_notes/release_20_02.rst
>
> diff --git a/ABI_VERSION b/ABI_VERSION
> index 9a7c1e503f..2e73f8d2aa 100644
> --- a/ABI_VERSION
> +++ b/ABI_VERSION
> @@ -1 +1 @@
> -20.0
> +20.1
> diff --git a/VERSION b/VERSION
> index 22131b00aa..7b50df9859 100644
> --- a/VERSION
> +++ b/VERSION
> @@ -1 +1 @@
> -19.11.0
> +20.02-rc0
20.02.0-rc0 ?
The rest lgtm.
--
David Marchand
next prev parent reply other threads:[~2019-12-02 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:57 Thomas Monjalon
2019-12-02 15:29 ` David Marchand [this message]
2019-12-02 15:40 ` Bruce Richardson
2019-12-02 15:43 ` Kinsella, Ray
2019-12-02 16:13 ` Thomas Monjalon
2019-12-02 16:27 ` Kinsella, Ray
2019-12-03 10:10 ` 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=CAJFAV8zzOKrAQH1eT6Ce6LiNHBmDXseDnwDrZWh+Cpxa+E1ncw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=ray.kinsella@intel.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).