Heads up: Early Feature request deadline for SLE 15 SP4 / Leap 15.4 is on 26th June 2021
Hello openSUSE! 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, not for 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 exclusive 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 Alpha. Just to clarify, this deadline is the same for everyone be it a largest 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-utils 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 on Monday's meeting at 3:00 CEST ( https://meet.opensuse.org/FeatureRequests). More details about jira access and meeting at https://en.opensuse.org/Portal:Jump/Policy/CommunitySLEChangeRequests#Weekly... 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 cause 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 changes to these packages would result in package forks in SP4. Therefore it's 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 (https://en.opensuse.org/ECO ). These are just bit more complication to pass and it generally takes 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 with reporting and deduplication on the SUSE side. I'm processing requests together with Neal Gompa and others who join our call on Mondays. Neal and I would like to work on opening the request even further to the community (Most likely by skipping the jira.suse.com from initial 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 or 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. Lubos Kocman Release Manager openSUSE Leap
On Mon 2021-05-31, Lubos Kocman wrote:
This is important to keep in mind if you plan to update Leap exclusive 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.
As a practical note, I've always been told to focus on the "Why?" and "What?" not the "How?" when requesting features. In other words, one such request might be "Provide underlying libraries to support an upgrade to KDE 99.42 KDE as currently in Leap 15.3 consumes a number of libraries Leap inherits from SLES 15 SP3. We plan on updating Leap 15.4 to KDE 99.42 which will require newer versions of several of these, including · libqt5 > 9.19 · libruffle17 > 47.11 : and possibly others." And probably https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/... Hope this helps - file away! :-) Gerald PS: Note how I am not talking about upgrading those libraries, just providing, even if the outcome may just that ... an upgrade. That is not the need, however.
On Mon, 2021-05-31 at 17:49 +0200, Gerald Pfeifer wrote:
On Mon 2021-05-31, Lubos Kocman wrote:
This is important to keep in mind if you plan to update Leap exclusive 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.
As a practical note, I've always been told to focus on the "Why?" and "What?" not the "How?" when requesting features.
In other words, one such request might be
"Provide underlying libraries to support an upgrade to KDE 99.42
KDE as currently in Leap 15.3 consumes a number of libraries Leap inherits from SLES 15 SP3. We plan on updating Leap 15.4 to KDE 99.42 which will require newer versions of several of these, including
· libqt5 > 9.19 · libruffle17 > 47.11 :
and possibly others."
And probably https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/...
Actually high level wiki page for request planning is not a good idea. Yes we absolutely want to understand why are we doing the change, that one needs to be captured there as well. Thank you for pointing it out. I'll create the wiki page once today's GA tasks are done.
Hope this helps - file away! :-)
Gerald
PS: Note how I am not talking about upgrading those libraries, just providing, even if the outcome may just that ... an upgrade. That is not the need, however.
On Wed, 2021-06-02 at 08:19 +0200, Lubos Kocman wrote:
On Mon, 2021-05-31 at 17:49 +0200, Gerald Pfeifer wrote:
On Mon 2021-05-31, Lubos Kocman wrote:
This is important to keep in mind if you plan to update Leap exclusive 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.
As a practical note, I've always been told to focus on the "Why?" and "What?" not the "How?" when requesting features.
In other words, one such request might be
"Provide underlying libraries to support an upgrade to KDE 99.42
KDE as currently in Leap 15.3 consumes a number of libraries Leap inherits from SLES 15 SP3. We plan on updating Leap 15.4 to KDE 99.42 which will require newer versions of several of these, including
· libqt5 > 9.19 · libruffle17 > 47.11 :
and possibly others."
And probably https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/...
Actually high level wiki page for request planning is not a good idea. I wanted to write not a bad idea and then exchanged words. Sorry. Definitely a good idea :)
Yes we absolutely want to understand why are we doing the change, that one needs to be captured there as well. Thank you for pointing it out.
I'll create the wiki page once today's GA tasks are done.
Hope this helps - file away! :-)
Gerald
PS: Note how I am not talking about upgrading those libraries, just providing, even if the outcome may just that ... an upgrade. That is not the need, however.
Hello openSUSE! 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: https://en.opensuse.org/Feature_Planning_15.4 https://meet.opensuse.org/FeatureRequests Wiki is open for editing, so feel free to edit it directly in case that you can't attend. Thank you Lubos On Mon, 2021-05-31 at 06:09 +0200, Lubos Kocman wrote:
Hello openSUSE!
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, not for 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 exclusive 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 Alpha. Just to clarify, this deadline is the same for everyone be it a largest 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- utils 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 on Monday's meeting at 3:00 CEST ( https://meet.opensuse.org/FeatureRequests). More details about jira access and meeting at https://en.opensuse.org/Portal:Jump/Policy/CommunitySLEChangeRequests#Weekly...
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 cause 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 changes to these packages would result in package forks in SP4. Therefore it's 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 ( https://en.opensuse.org/ECO ). These are just bit more complication to pass and it generally takes 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 with reporting and deduplication on the SUSE side. I'm processing requests together with Neal Gompa and others who join our call on Mondays. Neal and I would like to work on opening the request even further to the community (Most likely by skipping the jira.suse.com from initial 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 or 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.
Lubos Kocman
Release Manager openSUSE Leap
participants (2)
-
Gerald Pfeifer -
Lubos Kocman