From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2] remove RaspberryPi support
Date: Tue, 12 Feb 2019 12:39:19 +0100 [thread overview]
Message-ID: <20190212113919.GI805@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20190212093036.23464-1-claudius.heine.ext@siemens.com>
On Tue, Feb 12, 2019 at 10:30:36AM +0100, claudius.heine.ext@siemens.com wrote:
> RaspberryPi is removed from meta-isar, because
> - there currently no maintainers for it
> - there is no automated boot test for it
> - forces burden on rest of isar to support jessie
> - very old board, most users should have moved on to RPi 2 or 3
>
> If those points change, support for it can be readded.
- There is a maintaner (the process has to be improved)
- Testing doesn't have to be automated (automation desired mid- to long-term)
- There is value in supporting old boards as long as it is reasonable
- I think we should strive for evolution and not discrete add-remove jumps
The burden issue demonstrates one of the fundamental ideas behind Isar. After
some time, people end up building for different suites. Many people who release
stretch today will build for stretch and buster tomorrow. Maybe now is the time
to make pluggable mechanisms for different suites. Without satisfying that
need, Isar won't be serving people in the long run, IMHO.
Regarding rpi1, I'd be reluctant to remove without understanding what went
wrong first. Moving to stretch shouldn't be a problem, but the issue of
elegantly supporting different suites remains nonetheless.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-02-12 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 12:41 [Discussion] Deprecating Raspberry Pi Claudius Heine
2019-02-11 12:48 ` Jan Kiszka
2019-02-11 13:30 ` Claudius Heine
2019-02-11 13:51 ` [PATCH] remove raspberry support claudius.heine.ext
2019-02-11 14:03 ` Jan Kiszka
2019-02-12 9:30 ` [PATCH v2] remove RaspberryPi support claudius.heine.ext
2019-02-12 11:39 ` Baurzhan Ismagulov [this message]
2019-02-12 12:41 ` Claudius Heine
2019-02-12 16:40 ` Baurzhan Ismagulov
2019-02-12 16:49 ` Claudius Heine
2019-02-17 10:16 ` Baurzhan Ismagulov
2019-02-11 14:03 ` [Discussion] Deprecating Raspberry Pi Baurzhan Ismagulov
2019-02-11 14:11 ` Claudius Heine
2019-02-11 14:27 ` Baurzhan Ismagulov
2019-02-11 15:17 ` Claudius Heine
2019-02-17 10:44 ` Baurzhan Ismagulov
2019-02-18 8:44 ` Claudius Heine
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=20190212113919.GI805@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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