Language Selection

English French German Italian Portuguese Spanish

Bringing Leap and SUSE Linux Enterprise closer together - a proposal

Filed under
Hi everyone,

today I have some exciting news and a proposal to relay: SUSE wants to
go another step in openness towards the openSUSE community and suggests
to bring the relationship of openSUSE Leap and SUSE Linux Enterprise to 
a new level.

Internally this idea is called "Closing the Leap Gap" and proposes to
strengthen and bring more closely together:

 * developer communities, by focusing on openSUSE Leap as a 
   development platform for communities and industry partners;
 * user communities, by leveraging the benefits of both a stable
   Enterprise code base and the speed of community contributions;
 * the code bases of openSUSE Leap and SUSE Linux Enterprise (SLE), 
   by not only sharing sources, but also offering the SUSE Linux 
   Enterprise binaries for inclusion in openSUSE Leap.

The proposal includes a three step approach:

 1. Merge the code bases for the intersection of openSUSE Leap 15.2 
    and SUSE Linux Enterprise 15 SP2 as much as possible without loss 
    of functionality or stability. (SUSE has started a cleanup process 
    on the SUSE Linux Enterprise side already.)
 2. In parallel to classic openSUSE Leap 15.2 create a flavor leveraging
    SLE binaries, leading to an intermediate release in the October 2020
    time frame.
 3. Build openSUSE Leap 15.3 with SLE binaries included by default
    (assuming community agreement).

As you can imagine, a number of people have been involved with this
so far, and I'd like to pull some of them in front of the curtain in 
a little interview.

Q: Thomas, all of engineering at SUSE reports to you, and I know 
   openSUSE is something you care about quite a bit.  What is SUSE  
   putting on the table here?

Thomas Di Giacomo: Let me step back, and give you a perspective as I see
  it. SUSE for 27+ years has been a part of global open source ecosystem
  that includes a vast number of developers, end users, communities,
  and organizations of all sizes working together and benefiting from
  the collective work. Most of our engineers are involved as well with
  some open source communities that they feel passionate about.

  Open source communities are an integral part of who we are and the
  ecosystem we serve. Naturally, we feel responsible to support the
  communities and the work done by them. openSUSE is no different and
  is actually even more special and very dear to SUSE. So, it should
  come as no surprise that we are fully committed towards the openSUSE
  project(s) and its community. It makes us all feel proud to see Leap
  and Tumbleweed grow and evolve, together with SUSE Linux Enterprise.
  This effort of our engineers working together with others in the
  openSUSE community will benefit everyone involved for many years 
  to come.

Q: And why are you doing this?

Thomas: We want open source to succeed for everyone – developers,
  contributors to end users and everyone in between. The benefits of
  open source are tremendous when the ecosystem grows as a result of
  the positive virtuous cycle of – contributing more, supporting the
  contributions, benefiting from contributions, which inspires more
  people contributing, and it goes on to grow as an upward virtuous spiral.

  We feel fortunate to be in the position of seeing the openSUSE community
  grow in tandem with the success of SUSE Linux Enterprise, and both
  feeding off each other to grow even more. This idea definitely goes in
  that direction. Now, let me defer to Matthias who came up with this idea.

Q: Okay, so, Matthias, first of all: what is your role at SUSE?

Matthias Eckermann: I am leading the Product Management team for 
  Linux platforms, covering SUSE Linux Enterprise, Edge, and Security.

Q: And what made you propose this?

Matthias: My team and I realized that the engagement of our SLE 
  business with the openSUSE community does not fully fit our view 
  on openness, and that mutual benefits are not leveraged sufficiently.

  We discussed what it would take to bridge the gap and bring the
  relationship to the next level. Beyond a common ground on the
  technical side, the code streams, this requires learning from each
  other; for example, we need to re-establish an open feature process
  between community, SUSE, and our industry partners.

  Thus we developed "Closing the Leap Gap", and - to test whether it
  might have a chance to fly - we outlined the initial idea with the
  openSUSE Board before going for approvals by SUSE management.

Q: You mention the board, so let me ask.  What is your take?
   What opportunities, benefits do you see?  What risks?

Dr. Axel Braun: With this change, we can make better use of our
  resources, as two code bases converge - so one build target less to
  consider. Everyone who packages for Leap and for Package Hub will
  immediately benefit from this.

Marina Latini: It's really exciting to see how SUSE is trying to increase
  its support for Leap, reducing the existing differences between our
  openSUSE Leap and SLE. I can see this proposal as a way to be more
  inclusive, giving to the community the opportunity to contribute in 
  an easier way to Leap and giving the chance to bring the openSUSE 
  spirit also in an Enterprise product like SLE.

  On the other hand, every new move is a change and we need to be sure
  that the changes won't limit our community freedom to submit packages
  to Leap or won't slow down Leap for following the internal SUSE
  development model.

Q: Matthias, that sounds like some extra effort required.
   How is SUSE contributing, what is SUSE committing to?

Matthias: Indeed, there is quite some one-time effort needed to get
  (back) to the common ground; this is covered by SUSE engineering teams;
  two groups are heavily involved: The Open Build Service experts are
  designing a workflow for a smooth integration of the binaries, and
  for reducing the long term maintenance efforts for our community
  contributors. SUSE release managers and packagers are working hard
  to synchronize the code bases without losing functionality or quality.
  Hundreds of change requests have been filed already, and to get this
  done properly, we are delaying the release of SUSE Linux Enterprise
  15 SP2 to July.

  And we are willing to invest more, to drive the idea to success
  quickly: we would take the burden, to create an intermediate openSUSE
  Leap release in October 2020 which then would incorporate SUSE Linux
  Enterprise binaries into Leap the first time.

  Probably, Adrian can comment on the Build Service aspects, and Lubos
  what it means to developers within SUSE and to the community release

Q: So, Lubos, as release manager for Leap, what have you been doing
   so far, and what is the impact you see?

Lubos Kocman: I spent most of the time on collecting data regarding SLE
  and Leap differences and having follow-up discussions and transforming
  feedback into action items. Max and the rest of the openSUSE release
  engineering team meanwhile did an excellent job of keeping Leap release
  activities going forward.

  The idea of re-using should generally lower the effort on the Leap side.
  However, it comes with the price of increased complexity to bring all
  pieces together. A new process will allow external contributors to file
  feature or update requests directly to SLE. This will already help a lot.

Q: Is this an outcome bound effort, or time bound?  I know the SLE
   release schedule is a bit like a 300m tanker.

Lubos: It's both. I see this as a balance between what can we deliver,
  how, and to what date. It took quite some effort to create a plan
  acceptable by all involved teams. Splitting the work across the
  upcoming two releases seemed to be accepted well at least by 
  involved parties so far.

Q: So, that is SLE 15 SP2.  How about Leap 15.2?

Lubos: openSUSE Leap 15.2 will have to slip by about 8 weeks to incorporate 
  all changes from the SLE and align with its new schedule. I believe that 
  the release will find a great use for extra time since we're still 
  finishing the refresh of packages from Factory. The prototype will 
  be meanwhile available in parallel to the openSUSE Leap 15.2.

Q: How is that research proceeding, Adrian?

Adrian Schröter: We have an idea about the setup in
  I anticipate to have a first prototype of the build setup in next three
  weeks. And more important is how to develop the workflows to allow a
  more collaborative joint effort between SLE and openSUSE development.

  However, we must keep in mind that this is really an entire new way to
  develop a distribution. On one hand it makes a lot of sense to integrate
  for example the SUSE Backports (aka Package Hub) people directly in our
  development process. This will make our distribution development stronger.

  On the other hand, we also must find ways how to solve new problems.
  For example how to keep our builds for architectures not covered by
  SLES like Arm 32bit and RISC-V. Also the turn around times of submissions
  and build results will be a challenge in the initial setup. And last but
  not least, the installed systems and users may need to deal with more

  But we have one year to work on these problems in parallel to our
  stable distribution. And we are indeed looking forward to make 
  openSUSE and SLE development more beneficial than ever.

Gerald: Thanks everyone for your input.  I'll be sharing all this with
  openSUSE mailing lists, and am sure there will be further questions,
  offers to help, and other input, so please chime in there. has an FAQ with
more details.

Lubos is going to send a proposal with more details on the implementation
side to opensuse-factory@.

I suggest we focus technical discussions of this offer and proposals
there (opensuse-factory@) and general discussions on opensuse-project@.

So, what do you think?


Read more

OpenSUSE Leap + SUSE Linux Enterprise Planning To Move Closer

  • OpenSUSE Leap + SUSE Linux Enterprise Planning To Move Closer In 2020

    SUSE and the openSUSE community are working to move SUSE Linux Enterprise and openSUSE Leap closer together.

    A proposal sent out today with the interest of SUSE is for taking the openSUSE Leap and SUSE Linux Enterprise relationship to a new level. This new collaboration would more closely align the source trees of openSUSE Leap and SUSE Linux Enterprise Linux, including the use of SUSE Linux Enterprise binaries within Leap.

SUSE proposes synchronizing code streams, includes SLE binaries

  • SUSE proposes synchronizing code streams, includes SLE binaries for openSUSE Leap

    SUSE has sent a proposal to the openSUSE community about bringing the code streams of both SUSE Linux Enterprise and openSUSE Leap closer together. The proposal includes SLE binaries for the community version.

    Bringing the code streams closer together to provide full compatibility provides several advantages to the community going forward such as the use of higher-quality code due to the clean-up of spec-files, an improved relationship between the two distributions, easier bug reporting, less code streams to maintain, extensively tested packages and the inclusion of SLE supported architectures like s390x.

    “With this change, we can make better use of our resources as one code base converge, so one build target less to consider,” expressed openSUSE board member Axel Braun in an email sent out to the community about the proposal. “Everyone who packages for Leap and for Package Hub will immediately benefit from this.”

    The proposal provided a staged approach to implementing the vision. The email listed the following options: • Merge the code bases for the intersection of openSUSE Leap 15.2 and SUSE Linux Enterprise 15 SP2 as much as possible without loss of stability or functionality. (SUSE has actually started merging from Leap into SUSE Linux Enterprise.) • Create an intermediate openSUSE Leap flavor where SLE binaries are used inside (October 2020 time frame) in parallel to classic Leap 15.2. • Build openSUSE Leap 15.3 with SLE binaries included by default (assuming community agreement).

openSUSE & SUSE Linux Are Coming Closer

  • openSUSE & SUSE Linux Are Coming Closer

    openSUSE and SUSE are working on bringing their distribution even closers. So much so that SLE binaries will be available to openSUSE users and it will be easier for openSUSE users to easily migrate to enterprise-grade Linux. We sat down with Dr. Gerald Pfeifer, SUSE CTO and openSUSE chair and Matthias Eckermann, Director Product Management, Linux Platforms.

Bringing openSUSE Leap and SLE closer

  • Bringing openSUSE Leap and SLE closer

    SUSE Linux is one of the oldest Linux distributions still in existence today, with a history that starts in 1994. Today it exists in a few forms, including the commercial SLE offering, which mainly targets the server market.

    The openSUSE project creates a community version of the SUSE distribution; its work is largely sponsored by SUSE (the company). OpenSUSE produces two main variants, the relatively stable openSUSE Leap and a rolling version called openSUSE Tumbleweed. Leap is built on packages from SLE, which form a stable base made up of relatively old software releases. For example, the Leap kernel version is the same as in the corresponding SLE version. The openSUSE team adds some changes to the SLE packages, then rebuilds them for Leap; the team also adds newer versions of some packages, such as desktop environments, from Tumbleweed. The current version of Leap is 15.1 (as of April 2020).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Python Programming

  • The PEPs of Python 3.9

    With the release of Python 3.9.0b1, the first of four planned betas for the development cycle, Python 3.9 is now feature-complete. There is still plenty to do in terms of testing and stabilization before the October final release. The release announcement lists a half-dozen Python Enhancement Proposals (PEPs) that were accepted for 3.9. We have looked at some of those PEPs along the way; there are some updates on those. It seems like a good time to fill in some of the gaps on what will be coming in Python 3.9

  • How to Write an Installable Django App

    In the Django framework, a project refers to the collection of configuration files and code for a particular website. Django groups business logic into what it calls apps, which are the modules of the Django framework. There’s plenty of documentation on how to structure your projects and the apps within them, but when it comes time to package an installable Django app, information is harder to find. In this tutorial, you’ll learn how to take an app out of a Django project and package it so that it’s installable. Once you’ve packaged your app, you can share it on PyPI so that others can fetch it through pip install.

  • Pros and Cons of Python: A Definitive Python Web Development Guide

    Python is a powerful programming language for mobile and web development projects. It is also the most popular programming language for AI in 2020. RedI Python development’s use cases in scientific computing, statistics, and education make it one of the highly preferred programming languages for Python programmers. The open-source programming language launched in 1992 is now on the verge of becoming the most popular and used programming language. Due to the rise in demand for AI and ML applications, Python web programming is now the first thing that comes to mind for coding such applications. But is Python for web development even worth it? It definitely is. Some of the top companies use Python web programming in their technology stack.

Fedora 32 Elections

mesa 20.1.0

Hi all,

I'd like to announce Mesa 20.1.0, the first release for the 20.1 branch.

Being the first release of this new branch, there can be issues that
will be discovered now that the new code will be widely used, so you may
want to stay on the 20.0.x releases until the 20.1.1 release, scheduled
for 14 days from now on 2020-06-10.

One already known issue that I want to point out is that Unreal Engine 4
has a bug in its usage of glDrawRangeElements() causing it to be
called with a number of vertices in place of the `end` parameter,
that was recently revealed. This is an annoying bug that we haven't
worked around yet. For more details:



Andrii Simiklit (1):
      i965/vec4: Ignore swizzle of VGRF for use by var_range_end()

Bas Nieuwenhuizen (4):
      radv/winsys:  Remove extra sizeof multiply.
      radv: Handle failing to create .cache dir.
      radv: Do not close fd -1 when NULL-winsys creation fails.
      radv: Implement vkGetSwapchainGrallocUsage2ANDROID.

D Scott Phillips (1):
      anv/gen11+: Disable object level preemption

Danylo Piliaiev (3):
      meson: Disable GCC's dead store elimination for memory zeroing custom new
      mesa: Fix double-lock of Shared->FrameBuffers and usage of wrong mutex
      intel/fs: Work around dual-source blending hangs in combination with SIMD16

Dave Airlie (1):
      llvmpipe: compute shaders work better with all the threads.

Eric Engestrom (4):
      .pick_status.json: Update to a91306677c613ba7511b764b3decc9db42b24de1
      tree-wide: fix deprecated GitLab URLs
      docs: Add release notes for 20.1.0
      VERSION: bump to 20.1.0 release

Erik Faye-Lund (1):
      zink: use general-layout when blitting to/from same resource

Gert Wollny (1):
      r600: Fix duplicated subexpression in r600_asm.c

Hanno Böck (1):
      Properly check mmap return value

Icecream95 (1):
      panfrost: Fix background showing when using discard

Jason Ekstrand (3):
      nir/lower_double_ops: Rework the if (progress) tree
      nir/opt_deref: Report progress if we remove a deref
      nir/copy_prop_vars: Record progress in more places

Kristian Høgsberg (1):
      freedreno: Use the right amount of &'s

Nataraj Deshpande (1):
      dri_util: Update internal_format to GL_RGB8 for MESA_FORMAT_R8G8B8X8_UNORM

Pierre-Eric Pelloux-Prayer (1):
      amd/addrlib: fix forgotten char -> enum conversions

Rhys Perry (1):
      nir: fix lowering to scratch with boolean access

Rob Clark (1):
      freedreno: clear last_fence after resource tracking

Samuel Pitoiset (2):
      radv: handle different Vulkan API versions correctly
      radv: update the list of allowed Android extensions

Timothy Arceri (2):
      glsl: stop cascading errors if process_parameters() fails
      glsl: fix slow linking of uniforms in the nir linker

Vinson Lee (3):
      r600/sfn: Initialize VertexStageExportForGS m_num_clip_dist member variable.
      r600/sfn: Use correct setter method.
      freedreno: Add missing va_end.

git tag: mesa-20.1.0
Read more Also: Mesa 20.1 Released With Numerous Linux Graphics Driver Improvements

Android Mirroring App ‘Scrcpy’ Just Added a Bunch of New Features

If you read this blog regularly enough you’ll be familiar with scrcpy, an ace root-free way to mirror your Android smartphone on your Ubuntu desktop and interact with it. Scrcpy is free, it’s open source, it’s awesome. Oh yeah, and it’s updated regularly! Which is what this post is about: telling you what’s new and notable in the latest release, scrcpy 1.14 — so let’s get to it! Read more