Testers wanted

[Unman]

Hello all,

Now that r3.1 is end of life, we need to do some work to clear the 113
bugs that are still open.

A first step would be to triage the bugs to see what still affects 3.2
and what can be closed.
If you are interested in helping out, please reply to me rather than to
the list. Ideally you will have a fairly vanilla 3.2 you can use for
testing. If you can send me a note of your hardware that would help in
allocating bugs where the original report referred to specific hardware.

With a bit of effort we should be able to clear these pretty quickly,
and you will have helped make Qubes that little bit better.

cheers

unman

[John Casey]

On Sunday, 2 April 2017 04:17:20 UTC+1, Unman wrote:

Hello all,

Now that r3.1 is end of life, we need to do some work to clear the 113
bugs that are still open.

A first step would be to triage the bugs to see what still affects 3.2
and what can be closed.
If you are interested in helping out, please reply to me rather than to
the list. Ideally you will have a fairly vanilla 3.2 you can use for
testing. If you can send me a note of your hardware that would help in
allocating bugs where the original report referred to specific hardware.

Apologies as I am not totally familiar with mailing list etiquette, but would it be better to include the mailing list so as to maintain a record of volunteers?

Regardless, I'm running 3.2 on a MBP Early 2013 (i5-3230M). I also am able to run on a desktop (GA-X99-UD4P, i7 5820k, GTX 660).

More than happy to help if I can.

 

With a bit of effort we should be able to clear these pretty quickly,
and you will have helped make Qubes that little bit better.

cheers

unman

Regards,

John 

[Eva Star]

On 04/02/2017 09:23 PM, John Casey wrote:

>>
> Apologies as I am not totally familiar with mailing list etiquette, but
> would it be better to include the mailing list so as to maintain a record
> of volunteers?
>

Or full list of tasks that need to do on some page and when done by
someone and reported to Unman then remove the task from the page.


--
Regards

[Jean-Philippe Ouellet]

You can just filter them:
https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.1+updates%22

Issues that get closed will disappear from that list automatically.

[Piit]

Am Sonntag, 2. April 2017 05:17:21 UTC+2 schrieb Unman:
> Now that r3.1 is end of life, we need to do some work to clear the 113
> bugs that are still open.
>
> A first step would be to triage the bugs to see what still affects 3.2
> and what can be closed.

> If you are interested in helping out, please reply to me [...]

Hello,

Qubes has become my major OS and I am happy to support this project.
While working in IT business I have another background/skillset than security/programming - if there are other ways to support you guys, let me know.

As such I am of course willing to support clearing up the bug list.

> Ideally you will have a fairly vanilla 3.2 you can use for
> testing.

Im running Qubes OS Release 3.2.

> If you can send me a note of your hardware that would help in
> allocating bugs where the original report referred to specific hardware.

I'm running Qubes on my Lenovo Thinkpad W540, I've attached my HCL report for you.

kind regards and thank you & the Qubes OS team for your effort to provide such an OS.

- Philipp

[drew....@gmail.com]

Tell me what hardware you want me to use and I'll use it.

I have multiple PCs, I'll get the HCL for them.

One is a Dell Precision T5500, Dual GPU, 1 x X5650 @ 2.67GHz with 24 GB RAM.

One is a custom PC, single GPU, single Q8400 CPU with 6 GB RAM.

I also run Qubes on my Laptop, an HP 8460p with 8 GB RAM and it is a Quad Core i7.