Hello openSUSE, I'd like to announce that we have a final no-Go for Leap 15.2.1 after talking to stakeholders or engineers working on blocking issues. **What does that mean? ** It means that we have developed at least an Alpha quality distribution prototype (openSUSE Jump) with almost finished maintenance support. It's just that it's not going to be immediately released into production as an intermediate release openSUSE Leap 15.2.1 (original GA date November 4th, 2020). **What are next steps?** Instead of that, we are going to use Jump as a basis for openSUSE Leap 15.3. openSUSE Leap 15.3 is going to be based on top of the existing Jump prototype from the very beginning. The development phase of openSUSE Leap 15.3 starts tomorrow (November 4th, 2020). https://en.opensuse.org/openSUSE:Roadmap With that said, I'd like to invite you all for our small virtual kickoff event tomorrow afternoon https://news.opensuse.org/2020/10/28/opensuse-community-to-kickoff-session-f... **What's the the current state CtLG implemnetation in openSUSE 15.3?** * https://en.opensuse.org/Portal:Jump:OBS:SRMirroring (IBS -> OBS sync) * handling of update-info metadata in the maintenance setup * seamless migration experience (no manual workarounds) * Improve Quality of aarch64 and ppc64le in openSUSE Backports * Filtering of NDA content (NDA liftoff is after SLE 15 SP3 Beta 1) - end of November * ARMv7 question, SLE core is not available for ARMv7. We've received recommendation from PM on Friday, to rebuild all packages for ARMv7 in Leap (was out of scope for 15.2.1). I believe that TODOs above will be addressed by the time we enter the Beta phase in February 2021 or sooner. -- Lubos Kocman, Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg - Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer