How to join the new Qubes OS testing team (message from deeplow & unman)

1 view
Skip to first unread message

Andrew David Wong

Jul 20, 2021, 8:59:37 PM7/20/21
to qubes-devel, qubes-users, qubes-testers, qubes-project
Dear Qubes Community,

The message below is from deeplow and unman. Here's the link to the
original post on the Qubes Forum:


# Joining the Testing Team

## 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

## What's the risk?

For those willing to enable the testing repositories for the [current
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 to join the testing team?

1. 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` saying you'd like to join (does not require
JavaScript or a forum account)

2. Follow the instructions for the kind of testing you want to help with
(testing updates / releases)

>Testing Type|Instructions|Description|
> --- | --- | --- |
>Testing Updates|[see
here](|Enabling the
testing repositories (e.g. 4.0 testing)|
>Testing Releases|[part 1
]( & [part
2](|Running the upcoming
Qubes version (e.g. 4.1) and enabling the testing repositories.|

3. Report issues in the appropriate category:
* **If testing updates**, post in the '4.0 Testing' category, or
email `testing-updates at` .
* **if testing releases**, post in the '4.1 Testing' category, or
email `testing-releases at` .

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.

Reply all
Reply to author
0 new messages