I am. I’ll do this this afternoon (EU time) or tomorrow at most.
Joining Message
The following will be the joining instructions. Any suggestions for changes?
What’s the testing team?
It’s a group of people who commit to testing updates or releases of Qubes OS and who are willing to provide test and confirm issues, or identify particular edge cases. This is key to detect issues early on and catch them before they affect more users.
What’s the risk?
For those willing to enable the testing repositories for the current release the risk is minimal to testers because any packages end up in current anyway.
However, if security is crucial in your case, you should strictly use the stable release, not enable the testing repositories and not join the testing team.
How to 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.org
saying you’d like to join (does not require javascript nor a forum account)Follow the instructions for the kind of testing you want to help with (testing updates / releases)
Report issues weekly in the appropriate category:
- If testing updates in the “4.0 Testing” category or by emailing the form
4.0-testing at forum.qubes-os.org
.- if testing releases in the “4.1 Testing” category or by emailing the forum
4.1-testing at forum.qubes-os.org
.You can leave the group at any time by following steps similar to the ones in
1.
Soft launch or hard launch?
Either are fine with me. We could do a soft launch Qubes-project-wise and a hard-launch on the forum, pinning the topic globally for a few weeks.