All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev <dev@dpdk.org>, Markos Chandras <mchandras@suse.de>,
	Panu Matilainen <pmatilai@redhat.com>
Subject: Re: RFC: DPDK Long Term Support
Date: Tue, 7 Jun 2016 14:36:15 +0200	[thread overview]
Message-ID: <CAATJJ0KK0XGCmjgb+Li1JOCzykK-SqpB6D8i4T6e+p+e396jgQ@mail.gmail.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20257B8E3@IRSMSX103.ger.corp.intel.com>

On Fri, Jun 3, 2016 at 5:07 PM, Mcnamara, John <john.mcnamara@intel.com>
wrote:
[...]
>
> LTS Version
> ------------
>
> The proposed initial LTS version will be DPDK 16.07. The next versions,
> based
> on a 2 year cycle, will be DPDK 18.08, 20.08, etc.
>

I can see on the discussions that much more things around this have to be
discussed and agreed, but to some extend we will also just "have to wait
and see" how things work out.
I fully agree to the API change argument to start with 16.07 and the 2 year
cycle (more would be nice, but this means effort and after a while almost
nothing is "easily" backportable).

Never the less I have to ask - as I'd be personally much more happy if it
would be the odd years autumn release that would make the LTS as it would
match our LTS releases much much better.
Otherwise we (Ubuntu) will always "just miss" the LTS by a few months.
First I'd have thought on xx.02 releases, but consuming applications might
need time to adapt and while there are the nice API/ABI guarantees
experience tells me to better leave some kind of time-buffer.

Also this would give all of us a first shot with a shorter (not so long as
in L) LTS to see if the process we defined works out before jumping on a
full 2 year cadence.

So while I see that this is kind of "my problem" I would at least try to
personally ask and vote for LTS being: 16.7, 17.11, 19.11, 21.11, ...

Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

  parent reply	other threads:[~2016-06-07 12:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 15:07 RFC: DPDK Long Term Support Mcnamara, John
2016-06-03 16:05 ` Thomas Monjalon
2016-06-06 11:49   ` Yuanhan Liu
2016-06-06 13:31     ` Thomas Monjalon
2016-06-06 14:14       ` Yuanhan Liu
2016-06-06 14:23         ` Thomas Monjalon
2016-06-07 13:17   ` Mcnamara, John
2016-06-03 18:17 ` Matthew Hall
2016-06-07 12:53   ` Mcnamara, John
2016-06-05 18:15 ` Neil Horman
2016-06-06  9:27   ` Thomas Monjalon
2016-06-06 13:47     ` Neil Horman
2016-06-06 14:21       ` Thomas Monjalon
2016-06-06 15:07         ` Neil Horman
2016-06-07 16:21       ` Mcnamara, John
2016-06-07 15:55   ` Mcnamara, John
2016-06-06 13:44 ` Nirmoy Das
2016-06-06 14:16   ` Yuanhan Liu
2016-06-07 12:36 ` Christian Ehrhardt [this message]
2016-06-07 19:39   ` Martinx - ジェームズ

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=CAATJJ0KK0XGCmjgb+Li1JOCzykK-SqpB6D8i4T6e+p+e396jgQ@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=mchandras@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.