Hi On 4/10/20 5:27 PM, Matwey V. Kornilov wrote:
09.04.2020 15:30, Adrian Schröter пишет:
On Donnerstag, 9. April 2020, 14:09:22 CEST wrote Stasiek Michalski:
Leap did become "the better SLE" overtime, so we should have seen this coming a mile away, but I do not know how to feel about SLE basically using all of that work that the community did to achieve this. Maybe SUSE should just wait with those kinds of changes for when they feel comfortable with openly developing SLE instead, because that does bring in some value to both Leap and SLE and doesn't take away any of the things that the community added to Leap.
We understand that we also need to allow SLE submissions during this project.
We don't know how exactly to achieve this right now, I have to admit.
But we have this year to work on this...
IMO, SLE submissions have to be enabled before anything else, because it is already an issue. Many times when I had tried to make a maintenance update or update some package in upcoming Leap, I saw the same: "this package comes from SLE". And then it easily may take months to resolve the issue.
If you feel like you are being held up in this area feel free to contact the board (or me). There are processes in place for this and when they work they work pretty well and efficiently, there are some places where its working really well. Unfortunately communication of these processes within SUSE hasn't always been fantastic so there are certain maintainers who are less aware of them, there are also sometimes where packages require new maintainers which can also take time. The SLE maintenance process is slightly more complex then the openSUSE one, due to the agreements SUSE has with its customers there are only certain things that we can normally process as a maintenance update (Leaps rules are much more flexible here), anything beyond that ends up needing management approval. Also unlike Leap all SLE maintenance updates go through a QA process, given the QA team has limited resources these updates are generally done in order of severity, so if there is a period where a larger number of security fixes need to go through then normal then sometimes other packages get held up. If you have a concern about a security related update then you can always contact the security team https://en.opensuse.org/openSUSE:Security_team So even with a more open development process which I hope we get at some point much of these processes will still need to stay the same and so the process will still likely take longer then the current leap process. Having said that some of the things listed in the first part of this email can be improved, but we can do that before moving to a shared development model. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B