On Tue, Oct 15, 2024 at 7:19 PM Lubos Kocman via openSUSE Factory <factory@lists.opensuse.org> wrote:
Hello Manfred
Max Lin will be mass-adding ~6k packages. But we should not just showel packages around, these should be also somehow tested. And our https://openqa.opensuse.org/group_overview/129 is rather limited now thanks to the new installer.
I'm ready to trigger updater script to submit packages to Leap 16.0 from Factory in case package has a successfully build on the pretest-project[1], package maintainer should received a review request for each created ones. And please note that, there is a limited list of package exist in pretest proejct[1], only package has been updated in last 1000 days to openSUSE:Factory project. If your maintained package(or your needs) does not submit to openSUSE:Leap:16.0 project via our script, you're welcomed to submit it to openSUSE:Leap:16.0 from openSUSE:Factory project. [1] https://build.opensuse.org/project/show/openSUSE:Leap:16.0:FactoryCandidates Regards, Max
Just submit packages that you use/need/miss to openSUSE:Leap:16.0, submissions will have to be reviewed by the maintainer anyway. I am especially interested in feedback such as "don't add mlocate since we already have plocate" etc, this is extremely useful and keeps our project fresh.
Lubos
On Tue, Oct 15, 2024 at 12:05 PM Manfred Schwarb <manfred99@gmx.ch> wrote:
Lubos,
Am 07.10.24 um 14:01 schrieb Lubos Kocman via openSUSE Factory:
Hello everyone!
(Also available in html https://news.opensuse.org/2024/10/03/leap-16-0-prealpha/)
[...]
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 https://en.opensuse.org/openSUSE: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.
I see that there is only a bare minimum of packages in https://build.opensuse.org/project/show/openSUSE:Leap:16.0
How is the policy of adding packages to Leap 16? Will there be an automatic import of all Leap 15.x packages into Leap 16?
Is the intention to keep the number of packages small, or shall there be as many packages (or more) in Leap 16 as in former Leap editions?
Do maintainers need to take actions to get their packages into Leap 16?
Sorry for these many questions, but I think some guidance is needed at this point. I see that you described some thoughts about package submission below, but for me this is not really concrete enough.
Thanks, Manfred
PS: and I really hope there will be some way to bypass the SLES-induced package blockage all over the place.
**Where to submit packages, how is it built, and where is it tested?**
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](https://en.opensuse.org/Portal:Jump:OBS:SRMirroring) 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 https://openqa.opensuse.org/group_overview/129. Later, we plan to rework the existing Leap 16.0 Images job group https://openqa.opensuse.org/group_overview/126 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 for Leap 16.0 enablement https://progress.opensuse.org/issues/164141 and upgrade from 15.6 https://progress.opensuse.org/issues/166562.
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.
Lubos Kocman on behalf of the openSUSE Release team
--
Best regards
Luboš Kocman openSUSE Leap Release Manager