On Apr 23, 20 21:13:58 +0200, Axel Braun wrote:
Am Donnerstag, 23. April 2020, 11:34:14 CEST schrieb Stefan Behlert:
AFAIK Lepa has the "installler sef-update" not enabled, so this would be
even more beneficial in such cases.
Can you explain what this is?
A typo - it should be "installer self-update".
On SLE - but not on Leap afaik - when you start the installer, it first
goes to a specific repository and "updates" itself with the packages inside
there. This could be an update of a package or a downgrade, it's
independent of version umbers used. Some checks are disabled, so the user
just gets what's there - even it might might break dependencies. Due to
that, this self-update is rarely used, and needs a lot of additional
testing and care-taking.
It allows on SLE that a customer who is still using an older version (due
to the life-time, e.g.) can install on newer hardware (if supported), and
to fix important installer bugs (which we avoid to have, of course;) ).
But be aware:
We have seen with SLE 15 SP1 that this is not "just" a simple
refresh. It requires work, updates of media configuration as well as
testing, and then you have to get it done at the "right" point in time. Or
you leave out a dependency, or miss an important security update.
The approach should be more like TW - a successful openQA test may even
trigger a new build. Toolchain should be in place, as this is how TW works
Sure, automation is key there.
This does not
mean Leap should not do it, but is a warnign that it's not
easy. And I wonder how often people really stumble into new hardware issues
before the next release. With SLE, this happens due to the long-time use of
the same Service Pack, but for Leap I would expect that people rather take
the latest version of Leap available, leaving only a 12 month timefrmae
where it may be needed to update the installer.
This complain was already raised more often, not only in german media, but as
well from users here. Sure, we all know that brand new hardware can be an
issue with nearly any Linux system. But we should try our best to give users a
positive experience with a solid system AND up to date drivers. 12 month is a
way too long time for this.
Well, you are for sure in a better position to judge if it's worth the work
- with automation in place it might be even less than feared. Adaption
of media content might still need manual work, but the rest could be
automated fairly easy - including automated deployment.
(I wonder, if it would not even work for Leap to do an update of the iso
every month once GA is reached)
Dr.-Ing. Axel K. Braun
PGP Fingerprint: 2E7F 3A19 A4A4 844A 3D09 7656 822D EB64 A3BA 290D
Public Key available at http://email@example.com
Personal Freedom starts with free/libre Software
ThinkPad T520 running openSUSE Tumbleweed 20200419
Stefan Behlert, SUSE Software Solutions
Product Manager SUSE Linux Enterprise
Maxfeldstr. 5, D-90409 Nuernberg, Germany
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-releaseteam+owner(a)opensuse.org