dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <ray.kinsella@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
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
Date: Mon, 2 Dec 2019 16:27:23 +0000	[thread overview]
Message-ID: <BN6PR11MB414577CB952CD06DD3B35F1490430@BN6PR11MB4145.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1894184.cZXkvyexap@xps>

+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.
> >
> 
> 
> 
> 


  reply	other threads:[~2019-12-02 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 14:57 [dpdk-dev] [PATCH] version: 20.02-rc0 Thomas Monjalon
2019-12-02 15:29 ` David Marchand
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 [this message]
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=BN6PR11MB414577CB952CD06DD3B35F1490430@BN6PR11MB4145.namprd11.prod.outlook.com \
    --to=ray.kinsella@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.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).