DPDK-dev Archive on lore.kernel.org
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
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
Date: Mon, 02 Dec 2019 17:13:27 +0100
Message-ID: <1894184.cZXkvyexap@xps> (raw)
In-Reply-To: <BN6PR11MB4145831B521AF97F2024DCD290430@BN6PR11MB4145.namprd11.prod.outlook.com>

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 index

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
2019-12-02 15:40   ` Bruce Richardson
2019-12-02 15:43     ` Kinsella, Ray
2019-12-02 16:13       ` Thomas Monjalon [this message]
2019-12-02 16:27         ` Kinsella, Ray
2019-12-03 10:10   ` Thomas Monjalon

Reply instructions:

You may reply publically 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=1894184.cZXkvyexap@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    --cc=ray.kinsella@intel.com \
    /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

DPDK-dev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \
		dev@dpdk.org
	public-inbox-index dpdk-dev

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git