Our current approach so far was to keep all the development in a single
branch. This also conforms to the Factory First Policy. This meant
Tumbleweed, Leap 15.5, SLE 15 SP5, and also ALP
I've learned, that we need to make incompatible changes because of,
e.g., dropping Wicked from ALP and Tumbleweed and replacing all with
NetworkManager. This would mean splitting into two codestreams and two
Edge: Tumbleweed, ALP (Factory First)
Stable: Leap 15.5, SLE 15 SP5 (No Factory)
We still expect that there will be quite some development in the Stable
branch for some time. Of course, bugfixes go to all "applicable"
branches where it makes sense anyway. So, is this doable? Do we have
resources to keep them in "sync" - but already different? Can we keep
both installers at the same time in Edge till D-Installer is mature enough?
Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner
SLE Department, SUSE Linux