Feature Planning 15.4

This is a page to keep track of early Feature requests for openSUSE Leap 15.4

Leap 15.4 will accept new features during the entire Alpha and Beta phase. RC is when we start accepting only important bugfixes. https://en.opensuse.org/openSUSE:Roadmap

Partner feature deadline for SUSE Linux Enterprise 15 SP4 is June 26th 2021. This is not deadline for submit requests, but rather for features to be reported. Leap 15.3 consumes binaries for 1/3 of all packages from SUSE Linux Enterprise. We should keep track of larger feature requests for these packages, that would have hard time to be approved later in the process.

Keep in mind that we have to very often update certain SLES libraries, so we can actually update the intended package in Leap 15.4

Deadline for SLE 15 SP4 Submit requests

February 2nd 2022 is a feature cutoff date for SLES, we have to respect it. February 16th is the code submission deadline for SLES 15 SP4 Public beta and also for openSUSE Leap 15.4 Beta. This is the ideal deadline, changes might still be accepted after but we may have extra struggle (additional ECO approval or so).

How can I make submit request against SUSE Linux Enterprise?

So you have an approved feature in code-o-o (respective jira) or a bug that you'd like to fix.

First check with osc meta if it's really a SLE package. Following example shows that Leap 15.4 inherits bash binaries from SUSE SLE 15 SP3 Updates, which is also where we need to send the submit request.

 $ osc meta pkg openSUSE:Leap:15.4 bash
 <package name="bash" project="SUSE:SLE-15-SP3:Update">
   <title>The GNU Bourne-Again Shell</title>
   <description>Bash is an sh-compatible command interpreter that executes commands

User can either rely on Submit request redirection to a proper package origin. Or force the destination project. Please do not use osc mr as this would always create request in openSUSE:Maintenance project, which will not work for SLE.

$ osc submitreq openSUSE:Leap:15.4 bash
$ osc submitreq SUSE:SLE-15-SP3:Update

More information about project structure can be found in openSUSE:Packaging_for_Leap.

suse-sle-reviewer review

Next step is that somebody from openSUSE:Suse_sle_review_team triggers manually on his machine osc jumpreview and either approves (mirrors) or rejects the change with a reasoning.

Missing issue references

The most common reason to reject the change is missing issue in the submit request (jsc#123456|bsc#123456|boo#123456) reference. SUSE Linux Enterprise has it as a hard requirement.

Jira issue references for Leap community features can be found in metadata of the issue https://code.opensuse.org/leap/features/issues. Format should be jsc#ABC-123456.

Feature review meeting

The weekly feature review meeting is happening every Monday 15:00-15:30 CEST, 9:00-9:30 EDT. We discuss and process new requests in https://code.opensuse.org/leap/features/issues

Jitsi url: https://meet.opensuse.org/meeting

Where to find or report requests?

All requests should be available in https://code.opensuse.org/leap/features/issues Users could use pag tool (cli for pagure) to list requests on cmdline.

Feature then needs to be transferred manually to jira. And later approved by product management.

Who can create partner issues in JIRA

Userws lkocman, Pharaoh_Atem, ggardet_arm, oreinert, DocB should all be able to create JIRA feature in openSUSE partner project. Transition of feature to R&D and PM approval can be done only by openSUSE TAM (lkocman and his ba ckup gyr). Please reach out to them diretly (@suse.com email or irc) if you're in a hurry.

Keeping distribution fresh

We would like to do a quick research on how many packages in their respective Factory versions would fail to rebuild on top of SUSE SLE 15 SP3:Update and make sure that we can do a major distribution refresh where it is reasonable.

Current test project can be found here: https://build.opensuse.org/project/show/openSUSE:Backports:SLE-15-SP4:FactoryCandidates

We should have initial data by 26th June. We expect to raise 150+ update request from this. Initial data will have to be reviewed by SLE Product Management