Codebase(s) and Branch(es)
Hi there, 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 branches: 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? Thx Lukas -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux
On 12/9/22 10:39, Lukas Ocilka wrote:
Edge: Tumbleweed, ALP (Factory First) Stable: Leap 15.5, SLE 15 SP5 (No Factory)
JFTR, Jiri says: Where the code needs to differ, I would try to keep ALP and Factory the same as much as possible and let SLE15-SPx lack behind. -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux
On Fri, 9 Dec 2022 11:06:42 +0100 Lukas Ocilka <lukas.ocilka@suse.com> wrote:
On 12/9/22 10:39, Lukas Ocilka wrote:
Edge: Tumbleweed, ALP (Factory First) Stable: Leap 15.5, SLE 15 SP5 (No Factory)
JFTR, Jiri says: Where the code needs to differ, I would try to keep ALP and Factory the same as much as possible and let SLE15-SPx lack behind.
Hi, to make it more interesting do not forget about nice and unique feature of d-installer that allows installation of multiple products So I would still do development in single branch and just decide in code if something is different (like wicked not available). This way we still keep ability of d-installer to install different products and we just change model from multiple branches one per code stream to single code stream that supports multiple products with different needs. Josef
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 branches:
Edge: Tumbleweed, ALP (Factory First) Stable: Leap 15.5, SLE 15 SP5 (No Factory) So, after discussing this with the ALP Network Workgroup: Tumbleweed is a community product and we haven't seen any real request to drop Wicked
On 12/9/22 10:39, Lukas Ocilka wrote: there. Additionally, TW installation media is still built using Linuxrc and installation-images that use Wicked (https://bugzilla.suse.com/show_bug.cgi?id=1206256) and it's a lot of work to change it. D-Installer is not yet mature enough to be used anywhere else than for the ALP prototype, so Steffen would need to adapt installation-images first. But then ... Jiri wants to have Factory (TW) and ALP the same code/base. -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux
On 12/13/22 11:55, Lukas Ocilka wrote:
So, after discussing this with the ALP Network Workgroup: Tumbleweed is a community product and we haven't seen any real request to drop Wicked there. Additionally, TW installation media is still built using Linuxrc and installation-images that use Wicked (https://bugzilla.suse.com/show_bug.cgi?id=1206256) and it's a lot of work to change it.
A little update on this... https://bugzilla.suse.com/show_bug.cgi?id=1206723 The base package 'filesystem' eliminates /etc/sysconfig/network structure: - Remove unused /etc/sysconfig/scripts - Remove /etc/sysconfig/network hierachy, not used by default anymore The year 2023 starts with a lot of fun. -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux
participants (2)
-
josef Reidinger -
Lukas Ocilka