Anonymous Remailer (austria):
> What does it mean to test Tails testing releases?
>From the top of my head:
- Play with the new features, see:
- Changelog:
https://git-tails.immerda.ch/tails/plain/debian/changelog
- Redmine view:
https://labs.riseup.net/code/projects/tails/issues?query_id=215
- Use it as you would use Tails otherwise. I personally which to doing
all my Tails work from the RC when it becomes available.
- If some changes are expected to improve hardware support, try things
on this hardware and maybe help us clean the list of known issues if
some are solved:
https://tails.boum.org/support/known_issues/
- We have a manual test suite on
https://tails.boum.org/contribute/release_process/test but this is
already covered by a closed team of trusted testers, so you shouldn't
spend much time on this.
> Is there a set of guidelines to follow? I haven't seen
> any list of ways and/or methods of testing.
Where did you look for that information? I'm asking this because maybe
we should improve the way we communicate about testing releases...
> Are we to test it like we would a game and try everything
> we could think of to find bugs?
That's always possible :)
> How many Tails testers are there? I don't see much
> activity in the testing ML so I assume it's a limited
> set of people who routinely test or off and on, right?
So, we have this list of trusted testers for the manual test suite. But
they don't coordinate on tails-testers. This mailing list is either, for
specific call for testing (for example when we were preparing UEFI
support) or for regular testers like you who want to report on testing
release candidates, and such. Right now there are 107 people subscribed
to tails-testers@??? but indeed not much traffic.
