Hello everyone! I’d like to announce the start of development and the public availability of what we currently refer to as Leap 16.0 pre-Alpha. Since this is...
Hello everyone!
I'd like to announce the start of development and the public availability of what we currently refer to as Leap 16.0 pre-Alpha. Since this is a pre-Alpha version, significant changes may occur, and the final product may look very different in the Alpha, Beta, Release Candidate, or General Availability stages. The installer will currently offer you Base, GNOME, and KDE.
Users can get our new Agama install images from get.opensuse.org/leap/16.0. The installer will currently offer you Base, GNOME, and KDE installation.
Leap 16.0 is a traditional distribution and a successor to Leap 15.6 with expected General Availability arriving in the Fall of 2025.
We intend to provide users with sufficient overlap so that 15.6 users can have a smooth migration, just like they're used to from previous releases.
Further details are available on our roadmap. The roadmap is subject to change since we have to respond to any SUSE Linux Enterprise Server 16 schedule changes.
Users can expect a traditional distribution in a brand new form based on binaries from the latest SLES 16 and community packages from our Factory development codebase.
There is no plan to make a Leap 15.7, however, we still need to deliver previously released community packages from Leap 15 via Package HUB for the upcoming SLES 15 SP7. This is why there are openSUSE:Backports:SLE-15-SP7 project and 15.7 repos in OBS.
<h5>Who should get it?</h5> This is a pre-alpha product that is not intended to be installed as your daily driver. I highly recommend starting with the installation in a virtual machine and becoming familiar with the online installer Agama.
The target audience for pre-Alpha are early adopters and contributors who would like to actively be part of this large effort. Adopters should consider booting Agama Media from time to time just to check compatibility with their hardware.
For non-contributor users, I highly recommend waiting until we have a Beta, which is expected in the late Spring of 2025.
<h5>How to report bugs?</h5> I'd like to kindly ask you to check our Known bugs wikipage before reporting a new issue. If you find a new issue that is likely to affect users, please feel free to add it to the page.
Specifically for Agama I highly recommend using github.com/agama-project and collaborating with the YaST team on suggestions and incorporating any changes.
For the rest of the components, the workflow isn't changing; just select version 16.0 for bug submissions.
<h5>Feature requests</h5> All changes to packages inherited from SLES 16 need to be requested via a feature request.
Feature requests will be reviewed every Monday at a feature review meeting where we'll convert code-o-o requests into JIRA requests used by SUSE Engineering where applicable.
The factory-auto bot will reject all code submit requests against SLES packages with a pointer to code-o-o.
You can get a list of all SLFO/SLES packages simply by running osc ls SUSE:SLFO:1.1:Build.
Just for clarification SLFO, SUSE Linux Framework One, is the source pool for SLES 16 and SL Micro 6.X.
I highly recommend using code-o-o to co-ordinate larger community efforts such as Xfce enablement, where will likely need to update some of SLES dependencies. This allows us to share the larger story and better reasoning for related SLES update requests. The list of features is also extremely valuable for the Release article.
<h5>Where to submit packages, how is it built, and where is it tested?</h5> Leap 16.0 is built in openSUSE:Leap:16.0 project where we will happily welcome any community submissions until the Beta code submission deadline in the late Spring of 2025. We intend to keep the previous development model and avoid forking SLES packages unless necessary. We no longer can mirror SLES code submissions from OBS into IBS. So all SLES 16 update requests have to be requested via feature requests.
For quality control, we have basic test suites based on Agama installations in Leap 16.0 job group. Later, we plan to rework the existing Leap 16.0 Images job group for testing the remaining appliance images.
The project where we maintain community packages is subject to change as we have not fully finalized yet how to make Package HUB; we may use a similar structure with Backports as in 15.3+).
Further test suite enablement is one of the areas where we currently need the most help. Related progress.opensuse.org trackers poo#164141 Leap 16.0 enablement and poo#166562 upgrade from 15.6.
Another area where you can help is new package submissions and related maintainer review of package submissions to Leap 16.0. These reviews make sense as we'd like to check with maintainers whether that software in a given version makes sense for inclusion into Leap 16.0, rather than blindly copying all packages over.
<h5>Involvement in branding and marketing efforts</h5> I'm very proud to announce fresh branding efforts and want to thank all the people who helped give Leap and Tumbleweed a new look. We plan to publish an article or a video about the changes, and further plans as we still have a surprise or two in our pocket.
Do you want to help us on this front? Spread the news and feel free to join the #openSUSE_Marketing Telegram channel(https://t.me/openSUSE_Marketing)! https://en.opensuse.org/openSUSE:Marketing_team
Many thanks to all who helped us to reach this point.
Lubos Kocman<br/> on behalf of the openSUSE Release team
Really cool project and a good read!
Maybe I am too deep into retro computing and such but my first reaction when I read the headline was "Oh great! A new game engine for the Acorn Archimedes computer." :)
Congratulations to everyone who took part. That's amazing.
I totally agree with you. openSUSE Tumbleweed is IMHO the most stable rolling release distro out there.
Arch and some of its derivatives are also nice but still not as stable or polished as Tumbleweed.
So much bullshit in so little text... Again a “news” site that quotes a report from another site but doesn't link to it (probably so most readers don't read the real article). The CNN article says nothing about a plan to “ethnically cleanse northern Gaza” (this is typical Hamas press bullshit). Israel simply wants the civilian population remaining in the Netzarim Corridor to withdraw from the area so they are not longer in line of fire. And it is not an official plan but a plan of a group of retired Israeli military generals. Here is the link to CNN: https://edition.cnn.com/2024/09/22/middleeast/netanyahu-gaza-hamas-expulsions-plan-intl/index.html
And regarding MEE (Wikipedia):
According to its critics, Middle East Eye began forming in London in 2013 as the Islamist influence of Al Jazeera began to wane; several Al Jazeera journalists subsequently joined the project. Jonathan Powell, a senior executive at Al Jazeera, was a consultant ahead of its launch and registered the website's domain names. Bassasso, a Kuwait-born Palestinian living in London, was the sole director of Middle East Eye's parent company, M.E.E. Limited. Bassasso was a former director for the Hamas-controlled Al-Quds TV.[1,2] David Hearst denied that Bessasso was the owner of the news site but refrained from divulging the real owner.
[1] https://www.thenationalnews.com/uae/new-london-connection-to-islamists-1.648408
[2] https://www.aei.org/foreign-and-defense-policy/middle-east/qatars-other-covert-media-arm/
I am not sure if I would trust a website which does not provide any information about ownership, funding, or has a director who worked for the Hamas which is designated as a terrorist group by a lot of countries. Nobody has to agree how Israel handles the situation, but also nobody should simply believe everything that is written on the Internet. War is bad and I think most of us can't even imagine how bad and cruel war can be. Websites like MEE play a big part in creating even more hatred and suffering in this conflict through false information.
I am still missing the sub-folders feature in the application menu. I hope that someday a developer shows mercy and bring back that feature.
I just use Kritas Image Split feature. But it would be nice to download a widescreen picture and just set it as a background for all monitors. We need to wait until someone will implement that feature.
On the right side there are power lines but I am not sure if the thin cables on the left are power lines. They are very thin. Maybe phone lines or telegraph cables.
Yeah. On my phone it looks also more like water than just a wet road.
... but also I presume road building techniques have come a long way in the last 100 years.
That's what I find so fascinating about old photos. You can see how quickly technology has developed in 100 years. And the development is progressing faster and faster every year.
To me it looks a bit like a wet and worn out bitumen road after heavy rain.
Most streets built before the early 1900s in NZ were made of macadam, which was highly suitable for horse-drawn vehicles. However, with the rise of motor traffic in the 1920s, many areas had to seek more durable options for road surfacing. The most frequently used material became asphalt or bitumen, which gained widespread use starting in the 1920s.
