DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Panu Matilainen <pmatilai@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Stable Releases and Long Term Support
Date: Wed, 17 Aug 2016 13:30:03 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2025B5412@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <f283de0d-0257-8b4f-86ef-6dd2ca92138e@redhat.com>



> -----Original Message-----
> From: Panu Matilainen [mailto:pmatilai@redhat.com]
> Sent: Wednesday, August 17, 2016 1:30 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK Stable Releases and Long Term Support
> 
> ...
>
> > ABI
> > ---
> >
> > The Stable Release should not be seen as a way of breaking or
> > circumventing the DPDK ABI policy.
> 
> I find this a strange thing to say about a stable/LTS release ABI. I had
> read the originating thread before seeing this, but it still made me go
> "Huh?" for several seconds. The problem perhaps being, the rest of the
> document addresses stable/LTS releases, but this statement speaks about
> normal development work going on elsewhere.
> 
> The earlier version had a mention about ABI/API breakage related to things
> what not to backport but that's entirely gone here. Given how important
> ABI + API stability is for stable/LTS releases, I think it deserves a
> special mention here. Maybe something more to the tune of:
> 
> ---
> ABI or API breakages are not permitted in stable releases, special care
> must be taken to when backporting.
> 
> The existence of stable release(s) does not lessen the need to comply to
> DPDK ABI policy in development work.
> ---

That seems reasonable. If I do an update to the doc or add it to the guides I'll update it with this.

> 
> With the exception of the ABI/API thing, this looks like a fair starting
> point to me. Time and experience will tell more.
> 

I also think that we will have to see how it goes. What is important is that we end up with something that is useful to the community and consumers.

John.
-- 


      reply	other threads:[~2016-08-17 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 12:33 Mcnamara, John
2016-07-28 13:01 ` Yuanhan Liu
2016-08-17 12:29 ` Panu Matilainen
2016-08-17 13:30   ` Mcnamara, John [this message]

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=B27915DBBA3421428155699D51E4CFE2025B5412@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=pmatilai@redhat.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
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).