![](https://seccdn.libravatar.org/avatar/c0cfd5b7246be604feb77f43a3c9626f.jpg?s=120&d=mm&r=g)
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? - what needs to be done to set this up? - will submission work 'as before'? - openQA testing? - any other business? Lets get the process started! Cheers Axel [1] https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/ thread/AKZ3MH3OPNYQIZEY4ZIXDODTIDNOB6TV/