public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Maintenance policies and early considerations I
Date: Thu, 22 Sep 2016 11:31:32 +0200	[thread overview]
Message-ID: <57E3A4F4.6050109@codethink.co.uk> (raw)

Hi,

during the Technical Committee Meeting, last Monday, Ben Hutchings 
brought to the attention of the participants several topics to consider. 
I would like to bring them here. This is the first one

++ When do CIP should pick up a kernel?

+++ Maintainability effort

New major versions of commercial Linux Distributions are released at 3-4 
year intervals, so that typically only 4 versions need to be supported 
at one time.  Given that CIP's support period is meant to be even 
longer, it won?t be sustainable to extend every 'long term' branch, but 
only takes on a new branch every 2-4 years.

+++ Backport effort

The longer the intervals between new CIP branches, the greater need 
there will be for CIP or individual members to backport new hardware 
support (which carries its own risks).

+++ Trade-off

This trade-off is perhaps the most difficult issue to decide.


Best Regards

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

             reply	other threads:[~2016-09-22  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  9:31 Agustin Benito Bethencourt [this message]
2016-10-27  6:07 ` [cip-dev] Maintenance policies and early considerations I Hidehiro Kawai

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=57E3A4F4.6050109@codethink.co.uk \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.org \
    /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