Reminder that we have an extended openSUSE Leap 15.4 early feature
planning/review meeting today in about 10 minutes. We will be online
for about 1:30h so feel free to stop by.
We'd like to collect additional inputs for anything that's larger than
breadbox and involves changes in SLE. Smaller changes can be generally
requsted/implemented until the RC phase.
Wiki is open for editing, so feel free to edit it directly in case that
you can't attend.
On Mon, 2021-05-31 at 06:09 +0200, Lubos Kocman wrote:
I'd like to communicate an early feature deadline for SUSE Linux
Enterprise 15 SP4, which is on 26th June 2021.
This deadline is for having requests reported in jira.suse.com
the actual code submit requests.
This is very important to openSUSE Leap 15.4 contributors as 1/3 of
Leap 15.4 binaries will be re-used with SUSE Linux Enterprise and
therefore submit requests are accepted there.
This is important to keep in mind if you plan to update Leap
package which depends on e.g. a library from SUSE Linux Enterprise.
This will be the most common type of request according to my current
experience from SP3.
I was personally a bit surprised to have this deadline so early even
prior the OBS setup, as last year had it shortly after the first
Just to clarify, this deadline is the same for everyone be it a
partner, community contributor or an employee.
openSUSE Leap and Package Hub exclusive packages will have similar
deadlines as described in https://en.opensuse.org/openSUSE:Roadmap
We're aiming for the Leap 15.4 GA in early June 2022, therefore
deadlines will only slightly vary from the previous release.
We already have to feature requests open for 15.4 (usage of appx-
instead of fb-utils-appx and update of python-pycairo to 1.20). If
you're interested and have some open questions, feel free to pop up
Monday's meeting at 3:00 CEST (
). More details about jira
access and meeting at
This call is mainly to identify very obvious updates or requests for
features that we'd like to have in SLE 15 SP4 and therefore inherited
to Leap 15.4. We'll have a harder time to justify requests that
massive rebuilds, have large impacts, or seem to be risky (package
renames etc) later in the development.
Here I'd like to clarify that SUSE Linux Enterprise uses a layered
structure and in many cases packages have to be updated in the oldest
supported code-stream. I recommend checking the true origin of the
package (see referenced wiki). Larger or backward incompatible
to these packages would result in package forks in SP4. Therefore
not so easy, but the openSUSE release team is here to help you.
Requests during later development cycle have a bit more complicated
path but there is processes for it as well (
). These are just bit more complication to pass and it generally
longer, so if you want to have less work, please request it early.
I'm acting as sort of a partner manager and I'm going to help you
reporting and deduplication on the SUSE side. I'm processing requests
together with Neal Gompa and others who join our call on Mondays.
and I would like to work on opening the request even further to the
community (Most likely by skipping the jira.suse.com
report), but I'm bit afraid we won't make it new few weeks.
If you're unsure, please reach out to me or Neal over telegram/Email
even irc or simply join the Monday afternoon call.
As a side note, SUSE Linux Enterprise 15 SP4 is considered to be the
feature release (Tick-tock model). Therefore, we have relatively free
hands with requests of updates as soon as they are backed by some
reasoning (I need this for x.y.z).
Thank you very much for your understanding.
Release Manager openSUSE Leap