version: 20.02-rc0
diff mbox series

Message ID 20191202145718.16407-1-thomas@monjalon.net
State Accepted
Delegated to: Thomas Monjalon
Headers show
Series
  • version: 20.02-rc0
Related show

Checks

Context Check Description
ci/iol-intel-Performance success Performance Testing PASS
ci/travis-robot warning Travis build: failed
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-compilation success Compile Testing PASS
ci/Intel-compilation fail Compilation issues
ci/checkpatch success coding style OK

Commit Message

Thomas Monjalon Dec. 2, 2019, 2:57 p.m. UTC
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?
---
 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

Comments

David Marchand Dec. 2, 2019, 3:29 p.m. UTC | #1
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.
Bruce Richardson Dec. 2, 2019, 3:40 p.m. UTC | #2
On Mon, Dec 02, 2019 at 04:29:06PM +0100, David Marchand wrote:
> 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.
> 
I like that idea too, though again no strong opinion either way.
Kinsella, Ray Dec. 2, 2019, 3:43 p.m. UTC | #3
QQ.

What do you plan to do then, when you go for longer periods of ABI stability?

Ray K

> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Monday 2 December 2019 15:40
> To: David Marchand <david.marchand@redhat.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; dev <dev@dpdk.org>; Neil
> Horman <nhorman@tuxdriver.com>; Kinsella, Ray <ray.kinsella@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] version: 20.02-rc0
> 
> On Mon, Dec 02, 2019 at 04:29:06PM +0100, David Marchand wrote:
> > 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.
> >
> I like that idea too, though again no strong opinion either way.
Thomas Monjalon Dec. 2, 2019, 4:13 p.m. UTC | #4
02/12/2019 16:43, Kinsella, Ray:
> QQ.
> 
> What do you plan to do then, when you go for longer periods of ABI stability?

Very good point Ray!
For longer periods it would not mach DPDK version number.

So we keep standard scheme of increasing by +1 every quarter?



> From: Bruce Richardson <bruce.richardson@intel.com>
> > On Mon, Dec 02, 2019 at 04:29:06PM +0100, David Marchand wrote:
> > > 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.
> > >
> > I like that idea too, though again no strong opinion either way.
>
Kinsella, Ray Dec. 2, 2019, 4:27 p.m. UTC | #5
+1

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday 2 December 2019 16:13
> To: Kinsella, Ray <ray.kinsella@intel.com>
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; David Marchand
> <david.marchand@redhat.com>; dev <dev@dpdk.org>; Neil Horman
> <nhorman@tuxdriver.com>
> Subject: Re: [dpdk-dev] [PATCH] version: 20.02-rc0
> 
> 02/12/2019 16:43, Kinsella, Ray:
> > QQ.
> >
> > What do you plan to do then, when you go for longer periods of ABI
> stability?
> 
> Very good point Ray!
> For longer periods it would not mach DPDK version number.
> 
> So we keep standard scheme of increasing by +1 every quarter?
> 
> 
> 
> > From: Bruce Richardson <bruce.richardson@intel.com>
> > > On Mon, Dec 02, 2019 at 04:29:06PM +0100, David Marchand wrote:
> > > > 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.
> > > >
> > > I like that idea too, though again no strong opinion either way.
> >
> 
> 
> 
>
Thomas Monjalon Dec. 3, 2019, 10:10 a.m. UTC | #6
02/12/2019 16:29, David Marchand:
> 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>
> >
> > --- a/VERSION
> > +++ b/VERSION
> > @@ -1 +1 @@
> > -19.11.0
> > +20.02-rc0
> 
> 20.02.0-rc0 ?
> 
> The rest lgtm.

Applied with this change.

Patch
diff mbox series

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
diff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst
index 26f4a97cce..24d927d33e 100644
--- a/doc/guides/rel_notes/index.rst
+++ b/doc/guides/rel_notes/index.rst
@@ -8,6 +8,7 @@  Release Notes
     :maxdepth: 1
     :numbered:
 
+    release_20_02
     release_19_11
     release_19_08
     release_19_05
diff --git a/doc/guides/rel_notes/release_20_02.rst b/doc/guides/rel_notes/release_20_02.rst
new file mode 100644
index 0000000000..30605a3239
--- /dev/null
+++ b/doc/guides/rel_notes/release_20_02.rst
@@ -0,0 +1,139 @@ 
+..  SPDX-License-Identifier: BSD-3-Clause
+    Copyright 2019 The DPDK contributors
+
+.. include:: <isonum.txt>
+
+DPDK Release 20.02
+==================
+
+.. **Read this first.**
+
+   The text in the sections below explains how to update the release notes.
+
+   Use proper spelling, capitalization and punctuation in all sections.
+
+   Variable and config names should be quoted as fixed width text:
+   ``LIKE_THIS``.
+
+   Build the docs and view the output file to ensure the changes are correct::
+
+      make doc-guides-html
+
+      xdg-open build/doc/html/guides/rel_notes/release_20_02.html
+
+
+New Features
+------------
+
+.. This section should contain new features added in this release.
+   Sample format:
+
+   * **Add a title in the past tense with a full stop.**
+
+     Add a short 1-2 sentence description in the past tense.
+     The description should be enough to allow someone scanning
+     the release notes to understand the new feature.
+
+     If the feature adds a lot of sub-features you can use a bullet list
+     like this:
+
+     * Added feature foo to do something.
+     * Enhanced feature bar to do something else.
+
+     Refer to the previous release notes for examples.
+
+     Suggested order in release notes items:
+     * Core libs (EAL, mempool, ring, mbuf, buses)
+     * Device abstraction libs and PMDs
+       - ethdev (lib, PMDs)
+       - cryptodev (lib, PMDs)
+       - eventdev (lib, PMDs)
+       - etc
+     * Other libs
+     * Apps, Examples, Tools (if significant)
+
+     This section is a comment. Do not overwrite or remove it.
+     Also, make sure to start the actual text at the margin.
+     =========================================================
+
+
+Removed Items
+-------------
+
+.. This section should contain removed items in this release. Sample format:
+
+   * Add a short 1-2 sentence description of the removed item
+     in the past tense.
+
+   This section is a comment. Do not overwrite or remove it.
+   Also, make sure to start the actual text at the margin.
+   =========================================================
+
+
+API Changes
+-----------
+
+.. This section should contain API changes. Sample format:
+
+   * sample: Add a short 1-2 sentence description of the API change
+     which was announced in the previous releases and made in this release.
+     Start with a scope label like "ethdev:".
+     Use fixed width quotes for ``function_names`` or ``struct_names``.
+     Use the past tense.
+
+   This section is a comment. Do not overwrite or remove it.
+   Also, make sure to start the actual text at the margin.
+   =========================================================
+
+
+ABI Changes
+-----------
+
+.. This section should contain ABI changes. Sample format:
+
+   * sample: Add a short 1-2 sentence description of the ABI change
+     which was announced in the previous releases and made in this release.
+     Start with a scope label like "ethdev:".
+     Use fixed width quotes for ``function_names`` or ``struct_names``.
+     Use the past tense.
+
+   This section is a comment. Do not overwrite or remove it.
+   Also, make sure to start the actual text at the margin.
+   =========================================================
+
+* No change, kept ABI v20. DPDK 20.02 is compatible with DPDK 19.11.
+
+
+Known Issues
+------------
+
+.. This section should contain new known issues in this release. Sample format:
+
+   * **Add title in present tense with full stop.**
+
+     Add a short 1-2 sentence description of the known issue
+     in the present tense. Add information on any known workarounds.
+
+   This section is a comment. Do not overwrite or remove it.
+   Also, make sure to start the actual text at the margin.
+   =========================================================
+
+
+Tested Platforms
+----------------
+
+.. This section should contain a list of platforms that were tested
+   with this release.
+
+   The format is:
+
+   * <vendor> platform with <vendor> <type of devices> combinations
+
+     * List of CPU
+     * List of OS
+     * List of devices
+     * Other relevant details...
+
+   This section is a comment. Do not overwrite or remove it.
+   Also, make sure to start the actual text at the margin.
+   =========================================================