From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: Anton Mikanovich <amikan@ilbers.de>,
isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: Dropping Debian Stretch support
Date: Sat, 10 Dec 2022 22:29:01 +0100 [thread overview]
Message-ID: <CAJGKYO62G2deD9W9yEYHt-H7x54bpz_8J+TVXbLkxVYfTZuW6g@mail.gmail.com> (raw)
In-Reply-To: <20221210190338.584dc392@md1za8fc.ad001.siemens.net>
On Sat, 10 Dec 2022 at 19:03, Henning Schild <henning.schild@siemens.com> wrote:
>
> Am Fri, 9 Dec 2022 20:24:13 +0300
> schrieb Anton Mikanovich <amikan@ilbers.de>:
>
> > Hi all,
> >
> > Debian Stretch state was moved to EOL long ago (since July 2020), so
> > we are going to end its support inside Isar.
> > This will allow us to get rid of many hacks inside Isar core and
> > single example packages.
> >
> > Did anyone against dropping Stretch support?
>
> The contrary, full support from my side!
>
Supporting a distribution like Stretch which is End-Of-Life since July
2020 slow down the development of ISAR project in many ways:
- prevents to adopt solutions not supported by Stretch
- pollute the project with code/configs that cannot be developed further
- increase the number of tests for validating the product
The correct approach in this case is to fork or branch the project and
develop the fork/branch independently. Time to time when necessary
some changes could be backported from the ISAR to the fork/branch.
Moreover, this approach allows the business and/or management to have
a specific view about the effort needed to support that branch/fork.
This last aspect is very important for computing correctly the
cost/value of supporting a legacy platform.
I hope this helps, R-
prev parent reply other threads:[~2022-12-10 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:24 Anton Mikanovich
2022-12-10 18:03 ` Henning Schild
2022-12-10 21:29 ` Roberto A. Foglietta [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=CAJGKYO62G2deD9W9yEYHt-H7x54bpz_8J+TVXbLkxVYfTZuW6g@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.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