Vanilla OS 2.0 Orchid - Initial Work
We are happy to announce Vanilla OS 2.0 Orchid! With significant changes that we'd like to go over, like changing the base to Debian Sid, OCI support in ABRoot and more.
Moving to Debian Sid
After discussions and considerations, we decided to move away from Ubuntu and base our distribution on Debian Sid.
For this reason, we changed the version name and codename, starting with 2.0 Orchid. We have decided to use Orchid as the codename, as Vanilla derives from Orchids.
There are a few reasons we switched to Debian Sid:-
- It is closer to a vanilla experience than in Ubuntu. There were efforts to revert Canonical’s opinionated workflow, but it was time-consuming. It forced us to focus on reverting these changes. Ubuntu provides a modified version of the GNOME desktop, which does not match how GNOME envisions its desktop. One of the high-level goals of Vanilla OS is to be as vanilla as possible, so we reverted many of these changes to reach that goal.
- There is no strong opinion on application distribution. Snap is the primary method to get apps on Ubuntu. Based on our testing and many sources online, there are a lot of issues that Snap hasn’t addressed currently, like slow startups, centralization, etc. We prefer to push open and cross-organization efforts, like Flatpak. Our switch to Debian Sid will also address a core issue brought to us by many in our community, that most native applications installed in apx’s Ubuntu container are a Snap transitional package, which doesn’t work inside the container.
- We get more flexibility in releasing updates with the switch. We didn’t have much flexibility in publishing Vanilla OS releases before, as we needed to follow Ubuntu’s release cadence.
- We are already familiar with deb packages and Debian.
So, how will we release updates?
Updates will be released whenever we deem them ready or when it is essential or critical (like security updates).
However, there were a few concerns regarding the switch, so we are taking a specific approach to address them.
Security and Stability
Some issues with rebasing to a rolling release model and using it as a point release model are increasing security risks and potentially decreasing stability.
We decided to limit the number of packages we ship directly to the user as much as possible to decrease the overall footprint. Vanilla OS provides a small base (excluding A/B partitions) and strongly encourages alternative technologies like apx, Distrobox, Nix and Flatpak. We will be referring to Debian Security Advisories.
Likewise, for stability, the limited amount of core packages shipped to the user means that we will only be testing the base image, as it is the only one officially supported.
If we run into stability and security issues down the line, then we will reconsider our decision.
OCI Support in ABRoot
We are introducing OCI support in ABRoot. It means we will have greater control over updates, with more time to test the images before a release. Updates will take care of downloading and extracting the update, avoiding the usage of the package manager and ensuring an exact copy of the system while still maintaining the changes imposed by the user. It means you will have a more stable and reliable system without compromises.
Installation and Post-installation
For a seamless installation experience, we have added “Express” and “Advanced” setup types.
Express provides an intuitive and straightforward process that lets you set up Vanilla OS quickly while the setup take care of the critical tasks for you.
Advanced setup is for tinkerers and users who need a customized installation for their use cases and workflows.
We have improved the setup to allow users to configure their accounts and preferences. It means the user can set up their name, username and password from a pre-installed Vanilla OS system the first time they boot into it instead of making the OEM do it for them.
We intend to distribute GNOME 44 in the next version of Vanilla OS, but this may depend on any slowdowns in the release by GNOME and the packaging of some libraries on Debian. We will then evaluate whether it will be possible to package GNOME 44 on our own and contribute to Debian if necessary.
This release will be shipped with Debian’s 6+ kernel, ensuring compatibility with the latest devices and peripherals.