So, it’s up to the situation and should be need basis.įurthermore, the team is also planning to reduce the number of packages in the ISO file to minimize the risks of the “unstable” nature of packages. For example, if some Debian sid PACKAGE gets a critical CVE fix, then you may get an immediate point release of Vanilla OS. It gives some breathing space to the small FOSS developers and contributors team.īut what would be the release model for future releases? The team will follow an ad-hoc release method which means the famous term applies – “it will be released when needed or ready”. You don’t need to follow the two releases per year cycle. In addition, moving away from the Ubuntu base give you a much more flexible release cadence. For example, the “slow startups, centralization” problems are not fixed in core snap, and snap doesn’t run inside Vanilla OS’s apx container. ![]() After several testing and community feedback, the team feels that the current snap problem doesn’t fit the use case of Vanilla OS. The second reason is the problem handling “snap”. Also, the GNOME shipped by Ubuntu is customized as per Canonical’s needs and vision. But why move away from Ubuntu?Īs the team says, more difficulties and effort have been spent “to revert Canonical’s opinionated workflow” which takes more development time. ![]() The next release of Vanilla OS will be named “2.0” “Orchid” because of these major changes. Vanilla OS 22.10 Kinetic Desktop Vanilla OS plans for Debian base
0 Comments
Leave a Reply. |