The stable version of Qubes OS 4.3.0 will be released after thorough testing, which will involve gathering and addressing bug reports. The timeline for the stable release will depend on the number and severity of bugs discovered during this testing phase. Users can upgrade to 4.3.0-rc1 either via a clean installation or by performing an in-place upgrade from the previous version, 4.2, but are encouraged to back up their data before proceeding.
For those interested in testing this release candidate, it’s crucial to report any encountered bugs to assist in refining the stable release. It's important to note that known issues include templates restored from a pre-4.3 backup continuing to target their original repositories, which does not affect fresh installations.
A release candidate is a software build that may become stable unless significant bugs are found. It is aimed at advanced users willing to test less stable versions. Minor releases, like this one, follow semantic versioning and introduce new features while maintaining backward compatibility with earlier versions of the same major release.
Overall, the Qubes OS community is encouraged to participate in testing the new release candidate to help ensure a smooth transition to the stable release. For more detailed technical information and a complete list of changes, users are directed to the Qubes OS 4.3 release notes and documentation
Qubes OS 4.3.0-rc1 released
The first release candidate for Qubes OS 4.3.0 has been released for testing, showcasing a variety of new features and enhancements compared to Qubes OS 4.2. The release features updates to Dom0, Xen, the default Fedora template, the Debian template, and the Whonix templates. Included are preloaded disposables, a device assignment focused on self-identity orientation, and enhanced Qubes Windows Tools. The stable release is contingent upon the quantity of bugs identified and their level of severity. The release schedule documentation outlines the procedure for gathering bug reports, prioritizing them, and addressing the issues. If required, a new release candidate is issued, and the process proceeds until a stable release is announced. Testers have the option to upgrade to Qubes 4.3.0-rc1 through a clean installation or by performing an in-place upgrade from Qubes 4.2. It is advisable to perform a complete backup prior to testing, and seasoned users are invited to participate in the testing team. A release candidate represents a software build that may evolve into a stable release, provided that no significant bugs are identified during testing. Minor releases maintain backward compatibility with previous versions of the same major release.
