On 24/06/2022 10.27, Axel Braun wrote:
Dear Geekos,
those who joined the openSUSE conference got aware that we have a completely new approach (ALP) on the desk.
But until this flies, we need to make sure that Leap stays attractive for the openSUSE community. In other words - Leap 15.5 needs to receive updates and new features - updated versions of Rust and Python, just to mention two burning topics, as both versions shipped as default in current Leap are already EOL.
We understand that SLE15-SP5, the basis of Leap 15.5, will be a 'no feature' release.
And this is exactly the problem. We need to update the application layer like in the development model before Closing-the-Leap-Gap, ideally from Tumbleweed.
In the release engineering meeting on 15.06. [1] this was discussed (briefly). A potential solution could be to collect these updates in a repo like openSUSE:Leap:15.5
The intention of this mail is to get the discussion about a solution started, in order to make Leap 15.5 great product, before ALP flies.
- Is a separate repo for application updates a feasible approach?
IMHO a separate repo would still be feasible and better than nothing. But it would be preferred to base on a SUSE:SLE-15-SP5:GA repository.
- what needs to be done to set this up?
I hope that can be answered by looking into the tasks that have been conducted for Leap 15.4: https://progress.opensuse.org/projects/opensuse-leap-15-4/issues?set_filter=1&status_id=%2A&tracker_id=4
- will submission work 'as before'?
not sure what that means
- openQA testing?
yes. The effort of testing Leap 15.5 if it has only minor differences to Leap 15.4 is very small.