On Mon, May 16, 2016 at 10:42:21PM +0200, ge...@riseup.net wrote: > On 16-05-16 10:57:03, Holger Levsen wrote: > > one problem debugging this is that this problem occurs only if+when > > there is a new upstream version of torbrowser to be updated too, which > > only happens every 6-8 weeks or so. > > Not sure if I'm missing something obvious here, but: If testing would > happen in a clean, new, environment (a virtual machine for example) each > time, one could run these tests multiple times without the need for any > releases or updates. (I could provide hardware for this for regular, > automated use or to set up a proof of concept.)
Hardware ressources are not the problem, we have plenty. as I tried to say above: the problem is, an update arrives, and people update their system. After this the update cannot be tested anymore (as people are understandably not really willing to go back to a backed up state and retest again). -- cheers, Holger
signature.asc
Description: Digital signature