If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
- 1 Who is the audience?
- 2 Is this a new thing?
- 3 Typical cases of SLE Feature requests
- 4 What about regular bugs?
- 5 How do I find package origin?
- 6 How can I create an SLE Feature Request?
- 7 How do I get updates about the progress?
- 8 What does "Change has to come from SLE" mean?
- 9 Current content workflow for openSUSE Leap including SLE Feature requests
- 10 Proposed content workflow for Jump
Who is the audience?
Both community and SUSE-internal contributors to openSUSE Leap who somehow need a change in one of packages which comes from SUSE Linux Enterprise (SLE). Please see an effort to capture these personas. openSUSE Leap contains roughly 4000 such packages with SLE origin as of today.
openSUSE Release team is here to help you in this regard.
Is this a new thing?
This is not new to openSUSE Leap. It has always been the case. We're just getting it formalized with the goal of making it easier and smoother over time. This is independent from Closing the Leap Gap proposal or the Jump prototype for a next release of openSUSE Leap.
Typical cases of SLE Feature requests
What about regular bugs?
Regular bugs are not in the scope of this process.
Please follow openSUSE:Submitting_bug_reports on how to submit a bug report. We'll be more than happy if you'll link the Factory submit request to the bug.
In most cases the final Submit Request (SR) will come from the SLE side and will then supersede any open openSUSE Leap SR against the package. Please keep this in mind.
How do I find package origin?
Use osc origin (zypper in osc-plugin-origin) to check where the package comes from. Packages which are subject to this process are those with origin SUSE:SLE*.
How can I create an SLE Feature Request?
- Create a Submit Request against openSUSE Leap.
First of all please keep in mind that we all need to respect openSUSE:Factory_development_model, so make sure that it was submitted to Factory as well. This also contributes to having the feature request processed more quickly.
The Release Manager(s) and Release Engineer(s) will process the request and create an SLE Feature requests in JIRA and request approvals. Submit Request will be linked to the feature request.
Having an SR available significantly speeds up the process even though the SR against openSUSE Leap is expected to be rejected in the end as the change comes via SLE.
- Create a bug report against openSUSE Distribution.
The Release Manager(s) process all bugs with no priority set (default P5 priority) and transform obvious Feature requests into SLE feature requests in JIRA.
If applicable you can reference a Submit Request against Factory or even a rejected Submit Request against openSUSE Leap. Please be aware that requests should respect the criteria for upcoming milestone. For example, if you submit a brand new feature request in RC or post-RC phase it will be most likely rejected or deferred to a next release.
- Reach out to openSUSE:Release_team on irc
Preferably Release Manager for openSUSE Leap on irc / #opensuse-factory for more guidance. Do not use simply file request via plain email.
How do I get updates about the progress?
We do currently provide a weekly updates on all SLE Community feature requests as part of Release Engineering Meeting Minutes. Minutes are also sent each Wednesday to opensuse-factory@ right after the meeting.
Unfortunately, there is currently no way to see updates from JIRA for non-SUSE people. This should change by autumn 2020, when we expect to have a proper process in place.
The request for a transparent process is already in place (JIRA-722 - SLE feature process for external openSUSE Leap Contributors).
Currently, the best way is to watch meeting minutes or ask Release Manager or Release Engineer for an update. See openSUSE Release team for more information.
What does "Change has to come from SLE" mean?
The current openSUSE Leap workflow receives an automatic submission from SUSE Linux Enterprise as soon as it's accepted in SLE.
The Portal:Leap:Jump workflow will simply sync the SLE binary containing the change as soon as it is built.
Current content workflow for openSUSE Leap including SLE Feature requests
Following diagram covers current situation and highlights problematic part of packages with SLE Origin, see red boxes and arrows.
Latest source for the diagram can be found 
Proposed content workflow for Jump
Respectively proposed content workflow for new openSUSE Leap
Latest source for the diagram can be found