From: Marc Sune <marcdevel@gmail.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: Panu Matilainen <pmatilai@redhat.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] On DPDK ABI policy
Date: Fri, 8 Apr 2016 10:29:10 +0200 [thread overview]
Message-ID: <CA+3n-TpTbrNpY8qMgYpgBMrUf4-s7uypatEX6Jc3kZ3-zUmyAQ@mail.gmail.com> (raw)
In-Reply-To: <20160407215213.GB28667@mhcomputing.net>
2016-04-07 23:52 GMT+02:00 Matthew Hall <mhall@mhcomputing.net>:
> On Thu, Apr 07, 2016 at 02:51:35PM +0300, Panu Matilainen wrote:
> > LTS releases could help the situation somewhat, but then again
> > people tend to still want those new fancy things backported (you
> > know, have the cake and eat it too) but that can't be done because
> > of ABI breakage, so they're forced to run the latest version anyway.
>
> RH and Debian / Ubuntu don't put features in LTS except extremely rarely.
> Generally only if there's severe functionality breakage or security issues
> and
> the rest is ignored, and for good reason, as this is much more reliable and
> simple and predictable.
>
> If people are so irrational they can't deal with that simple of a policy,
> NEXT_ABI, LTS, etc. is never going to help them.
>
> If people like to have backported stuff, yes of course we can make trees
> and
> branches for this, they are basically free in Git. But at that point
> community
> people in need of LTS forks of features need to step up to the plate to
> help
> out.
>
Completely agree.
Marc
>
> Matthew.
>
next prev parent reply other threads:[~2016-04-08 8:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 13:56 [dpdk-dev] DPDK namespace Thomas Monjalon
2016-04-05 14:13 ` Trahe, Fiona
2016-04-05 14:31 ` Trahe, Fiona
2016-04-05 14:31 ` Arnon Warshavsky
2016-04-06 5:26 ` Yuanhan Liu
2016-04-06 12:07 ` Panu Matilainen
2016-04-06 12:34 ` Ananyev, Konstantin
2016-04-06 14:36 ` Wiles, Keith
2016-04-06 20:21 ` Dave Neary
2016-04-07 8:22 ` Marc
2016-04-11 16:10 ` Don Provan
2016-04-11 16:28 ` Thomas Monjalon
2016-04-06 12:41 ` Jay Rolette
2016-04-06 12:51 ` Mcnamara, John
2016-04-07 9:18 ` Thomas Monjalon
2016-04-07 9:33 ` Panu Matilainen
2016-04-07 10:16 ` Marc Sune
2016-04-07 11:51 ` [dpdk-dev] On DPDK ABI policy Panu Matilainen
2016-04-07 21:52 ` Matthew Hall
2016-04-08 8:29 ` Marc Sune [this message]
2016-04-08 8:47 ` Marc Sune
2016-04-07 21:48 ` [dpdk-dev] DPDK namespace Matthew Hall
2016-04-07 22:01 ` 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=CA+3n-TpTbrNpY8qMgYpgBMrUf4-s7uypatEX6Jc3kZ3-zUmyAQ@mail.gmail.com \
--to=marcdevel@gmail.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
--cc=pmatilai@redhat.com \
--cc=thomas.monjalon@6wind.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).