What was Jump?
Jump was a prototype of how could openSUSE Leap look like once we're done with current release of openSUSE Leap 15.2. It's not supposed to be a parallel supported alternative to the openSUSE Leap. See Portal:Leap/FAQ/ClosingTheLeapGap for more information. Jump is also an implementation proposal of the Closing The Leap Gap effort.
See following video from Adrian regarding the current status of Jump from the openSUSE Virtual Summit 2020 . A related talk is also the Current and Future strategy for openSUSE Leap  which is also from openSUSE Virtual Summit 2020 2020.
Leap 15.2.1 details
The openSUSE Leap 15.2.1 Go-NoGo decision takes place on Tuesday 20th October 2020.
A list of package forks that need to be rebuild with is_opensuse 1 to preserve functionality. These packages are expected to be addressed in SUSE Linux Enterprise 15 SP3 and openSUSE Leap 15.3. This list can be also understood as a list of feature set differences in between openSUSE Leap 15.2 and SUSE Linux Enteprise 15 SP2 Update.
openSUSE Leap 15.2.1 received no-go and we've agreed that first openSUSE Leap release to implement the mechanism developed as part of jump will be openSUSE Leap 15.3
Please see our Portal:Leap/FAQ/ClosingTheLeapGap for more information about Closing the Leap Gap.
Where is the documentation for the new submit request workflow?
The Diagram of the new content workflow including SLE Community Feature requests can be found at Portal:Leap/SLEFeatureRequests.
- Change validation concept for openSUSE Jump
- Jump Change requests for SLE Packages
- Submitting requests to Jump
Newly created documents referenced in these policies
Who is in charge?
Team working on the proposal is openSUSE:Release_team. Please see "Where is the work tracked?" for individual task owners.
What about kernel?
See current plans on Portal:Jump/Kernel