What’s the testing team?
It’s a group of users who help make Qubes better.
They commit to testing updates and releases of Qubes OS, and are willing
to provide test results, confirm issues, and identify particular edge cases.
This is key to detecting issues early on, and stop them affecting more users.
Who should join?
Community members with demonstrated track-record of good quality contributions.
What’s the risk?
For those willing to enable the testing repositories for the current release
the risk is minimal, because the packages will end up in current anyway.
If security and stability are crucial to you, you should use the current stable release,
not enable the testing repositories, and not join the testing team.
How do I join the testing team?
- Request to join the testing team
- Via forum (preferred): request to join here (requires JavaScript and a forum account)
- Via email: send an email to
register-testing-team at forum.qubes-os.orgsaying you’d like to join (does not require JavaScript or a forum account)
- Follow the instructions for the kind of testing you want to help with (testing updates / releases)
- Report issues in the appropriate category:
- If testing updates, post in the ‘4.0 Testing’ category, or email
testing-updates at forum.qubes-os.org. - if testing releases, post in the ‘4.1 Testing’ category, or email
testing-releases at forum.qubes-os.org.
You can leave the group at any time by following steps similar to the ones in 1.
Packages move through the testing process quite quickly. Ideally you
would be able to update at least once a week.
When 4.1 moves toward release, we will see if we can test some of the
open issues in 4.0, and confirm they have been closed.