All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] legacy: drop old options (branch yem/drop-old-legacy)
Date: Sun, 28 Mar 2021 21:24:02 +0200	[thread overview]
Message-ID: <20210328212402.696e0207@windsurf.home> (raw)
In-Reply-To: <cover.1616878389.git.yann.morin.1998@free.fr>

Hello,

On Sat, 27 Mar 2021 21:53:28 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> We advertise that legacy symbols will be removed after two years.
> However, so far, we've be more lax than that, and we only dropped
> symbols after about 5 year have elapsed.
> 
> This series removes options in step, starting with the usual 5-year
> threshold, in 1-year increments, to eventually catch-up with the
> advertised 2-year threshold.
> 
> Additionally, a little shell snippet is added in the comments, to
> help eventually drop those legacy symbols when they are still used
> elsewhere (e.g. as legacy defaults).

In fact, I am not sure I agree with the rule that we should keep them
only 2 years. Indeed, for users that follow the LTS releases, 2 years
should be more than enough. But believe it or not, our 12 months
maintenance period is still considered too short by users who don't
always have the resources/skills to update once a year. So we still do
have users that upgrade quite infrequently.

Since the maintenance cost of those legacy options is essentially zero,
I am wondering if we really need to drop them. Should we change the
rule and drop the ones that are 5 years old for example ?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2021-03-28 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 20:53 [Buildroot] [PATCH 0/5] legacy: drop old options (branch yem/drop-old-legacy) Yann E. MORIN
2021-03-27 20:53 ` [Buildroot] [PATCH 1/5] legacy: add note about removing options Yann E. MORIN
2021-03-27 20:53 ` [Buildroot] [PATCH 2/5] legacy: drop options more than 5 years old Yann E. MORIN
2021-03-27 20:53 ` [Buildroot] [PATCH 3/5] legacy: drop options more than 4 " Yann E. MORIN
2021-03-27 20:53 ` [Buildroot] [PATCH 4/5] legacy: drop options more than 3 " Yann E. MORIN
2021-03-27 20:53 ` [Buildroot] [PATCH 5/5] legacy: drop options more than 2 " Yann E. MORIN
2021-03-28 19:24 ` Thomas Petazzoni [this message]
2021-03-28 19:52   ` [Buildroot] [PATCH 0/5] legacy: drop old options (branch yem/drop-old-legacy) Yann E. MORIN
2021-03-29  6:59     ` Arnout Vandecappelle
2021-03-29  8:04       ` Peter Korsgaard

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=20210328212402.696e0207@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.