There was a recent post on reddit
that made us take a look at how to present our lifecycle page
(https://en.opensuse.org/Lifetime) and info to be added to the marketing
of Leap 15.3.
There were several comments on reddit that can be summarized as there is
a lack of clear information on how long the lifecycle of Leap 15.x will
be going forward. When the info on https://en.opensuse.org/Lifetime was
originally written, there was some clarity on major versions lasting a
minimum of 36 months. We know Leap 42 and 15 exceeded that lifecycle. It
looks like we're at a point where we evolved and need to provide a bit
more clarity for people based on the reddit comments
I propose we change the lifecycle page to include the following
sentences and include the info in the marketing of Leap 15.3 and beyond
(for the foreseeable future):
Leap *Major Release* (15.x) extends maintenance and support until a
At present, a successor has not been declared; Leap 15's lifecycle fully
aligns with SUSE Linux Enterprise.
There is a projection as of March 2021 that Leap 15 will extend to Leap
Both major versions of Leap 42 and 15 were supported more than 36 months.
Any thoughts, changes, removals or additions to the above sentences.
after reading https://en.opensuse.org/openSUSE:Members, I understand that I can cancel my membership status with
immediate effect and forever.
To become a "Member Emeritus", with a "way back" into the community in case things might turn good again, I have to wait
for the status request and just not respond to it. But the last such request was almost 3 years ago. IIUC I need to stop
all actions on the mailing lists (might be a good idea ;-)) and packaging (not so good) for the bot to pick me up.
So is there a manual procedure to follow to become "Member Emeritus"?
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
I like to discuss the upcomming single common name for repositories for
Given that we use the Jump concept now with Leap 15.3, it makes no sense
that we offer by default
repositories in parallel for each OBS project anymore. The content should
be identical and it contradicts the purpose of having a binary
So, in near future OBS will change it's interface and allow basically only
to select one repository for "Code 15-3". You can decide to include Backports
or Leap packages on top of SLE 15 SP3 as build and install dependencies,
but no matter how you configure it as OBS user, the resulting repository
name should have the same name.
The big question is, what should this repository name be?
People need to understand that they can use it on openSUSE Leap 15.3 or
on any SUSE SLE 15 SP3 installation.
Do you have any suggestions?
Adrian Schroeter <adrian(a)suse.de>
Build Infrastructure Project Manager
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
(HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
The first review round of the openSUSE Leap 15.3 retrospective happened
as part of the openSUSE Conference last Saturday.
let's have at additional rounds, where we'll continue from where we've
ended last time (marked with "<break"). Three rounds should be
sufficient, based on the amount of data and our pace from the first
June 22nd - 7-8am UTC (9-10am CEST)
June 22nd - 15-16pm UTC (17-18pm CEST)
June 23rd - 7-8am UTC (9-10am CEST)
In all cases let's use our favorite collaboration space
https://meet.opensuse.org/bar for increased outreach.
Everyone is welcome to join!
The idea is to screen share, read through the data, collaborate with
reviewers on action items, etc, and hopefully, also categorize the
issue in the way how we did that in 15.2.
I'd like to make sure we process the data before the openSUSE Release
Team meeting this Wednesday. Where I'd already like to provide some
"summary" of what to focus on in Leap 15.4.
The working document for retro review can be found here:
openSUSE Leap Release Manager
we did have a massive gallera outage which effected also our lovely
etherpad on last Thursday therefore we still have a backlog to review.
Therefore I'm announcing two additional "morning" rounds of Leap 15.3
retro in our virtual /bar
June 28th - 9-10am UTC (11-12am CEST) https://meet.opensuse.org/bar
June 29th - 7-8am UTC (9-10am CEST) https://meet.opensuse.org/bar
I would really like these to be final, as we've spent enourmous time on
it already. So please expect some speed review.
More details at
As usually everyone is welcome to join and help us to make suggestions
for action items.
On Thu, 2021-06-24 at 09:25 +0200, Lubos Kocman wrote:
> Thank you Daniel!
> On Wed, 2021-06-23 at 16:31 +0200, Daniel Noga wrote:
> > Dne 23. 06. 21 v 15:24 Lubos Kocman napsal(a):
> > > line 586 Regression to Leap 15.1 and Leap 15.2 Outdated mesa,
> > > again,
> > > actually more than in Leap 15.2 . Currently not an issue for me,
> > > as
> > > an
> > > user of NVidia, but considering buy AMD card, that can be issue
> > > for
> > > me
> > > in future.
> > >
> > > ^ Please reference the existing bug or open a new bug so we can
> > > follow
> > > up on more details. I did ask Stefan Dirsch but he was not aware
> > > of
> > > anything specific.
> > > https://en.opensuse.org/openSUSE:Submitting_bug_reports
> > That is just bad formating from survey form, originally it was
> > every
> > point new line, but I see here, that new lines are lost.
> > "Regression complain" was to disabling preempt. Outdated mesa was
> > another point and only as fear for future, than affecting me
> > nowadays.
> > In 15.2 was already conservative with 2 major versions behind to
> > release
> > date, in 15.3 is even more convervative with 3 major versions
> > behind
> > (21.1 released in may, 21.0 in march, 19.3 in december)
I'm happy to announce that MyGNUHealth version 1.0 was released and is on the
way to Tumbleweed.
MyGNUHealth is a joint effort by the GNU Health and KDE teams.
It is a personal digital health record with focus on security and privacy,
that puts you in control over your data.
It is designed to run on smartphones like the pinephone or the plasma-desktop.
Find the announcement here: