Opened 8 years ago

Closed 7 years ago

Last modified 19 months ago

#3846 closed task (fixed)

Recruit build test/signoff volunteers

Reported by: mikeperry Owned by: mikeperry
Priority: Immediate Milestone:
Component: Applications/Tor bundles/installation Version:
Severity: Normal Keywords: MikePerry201205
Cc: Sebastian, tagnaq@…, sam@…, unknown@…, phoul@…, twilde@…, runa, tichodroma@… Actual Points: 5
Parent ID: Points: 5
Reviewer: Sponsor:

Description

I still think it is a good idea to get tor-talk volunteers to commit to testing builds for us. We created this table for them to fill in but then forgot about it: https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff

There also used to be a pastebin or google doc with a testing checklist + instructions in it? Is that lost forever?

Child Tickets

Change History (25)

comment:1 Changed 8 years ago by mikeperry

Woo hoo! Found it in irc logs. http://etherpad.mozilla.org:9000/6yZdWhgBWF

comment:2 Changed 8 years ago by mikeperry

Merged that etherpad into our wiki.

comment:3 Changed 7 years ago by mikeperry

Cc: Sebastian added
Priority: normalcritical
Type: defecttask

Our non-Linux builds are a nightmare. Can we get on this already? :)

I can begin collecting some urls and describing more tests for people to run (#5292) if it will help speed this along/make it more valuable.

comment:4 in reply to:  1 Changed 7 years ago by arma

Replying to mikeperry:

Woo hoo! Found it in irc logs. http://etherpad.mozilla.org:9000/6yZdWhgBWF

https://etherpad.mozilla.org/6yZdWhgBWF appears to be the better (working) link now.

comment:5 Changed 7 years ago by mikeperry

FYI: Please use our wiki page at https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff instead of the etherpad for updating test lists. The etherpad was merged in to that page in comment 3.

Other reasons to formalize and distribute our testing process include guarding against things like WebSocket regressions and the myriad Antivirus software issues like #5689.

comment:6 Changed 7 years ago by tagnaq

Cc: tagnaq@… added

comment:7 Changed 7 years ago by mikeperry

Until we develop #5292 and collect all of our tests ourselves, we can use tests from https://www.torproject.org/projects/torbrowser/design/#Testing as well as http://samy.pl/evercookie and of course our friend from #5741, http://bitcoincharts.com/. Feel free to paste others in #5292 too.

comment:8 Changed 7 years ago by SamWhited

Cc: sam@… added

comment:9 Changed 7 years ago by Tichodroma

Cc: tichodroma@… added

comment:10 Changed 7 years ago by unknown

Cc: unknown@… added

comment:11 Changed 7 years ago by mikeperry

Priority: criticalblocker

Alright great, we got some interested people. I think we should start distributing builds to them for the next TBB release that isn't a time critical security issue. I'm going to set this ticket as 'blocker' as a way of saying "Don't release the next TBB until we at least get it to the people who volunteered to test it first."

Of course, if there is another blocker security issue filed between now and then that is time critical to release a fix for, we can skip figuring this testing process out for it. But for all other normal TBB releases, we should be exercising a volunteer testing process ASAP.

comment:12 Changed 7 years ago by phoul

Cc: phoul@… added

comment:13 Changed 7 years ago by hartmut

I like to help also

comment:14 Changed 7 years ago by twilde

Cc: twilde@… added

comment:15 Changed 7 years ago by cypherpunks

Can people with no code-writing capabilities also join your testing process?

These testing pages like "ip-check.info", "samy.pl/evercookie" and other sites as well as the step-by-step testing instructions on "https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff" seem to be easy enough for advanced users who have no idea how to write code.

comment:16 in reply to:  15 Changed 7 years ago by mikeperry

Replying to cypherpunks:

Can people with no code-writing capabilities also join your testing process?

Yes. We're still discussing specifics internally, but most likely the way this is going to work is that a set of urls with builds will get emailed out to all interested parties with a time limit to reply with feedback. If no feedback arrives within that timeframe, the build will be published anyway. So I think this means that we want to widen the net as far as people who volunteer to actually test builds, especially since it will also mean increased opportunity to test more OS versions, Antivirus versions, etc.

However, long term, we're hoping to use this manual process to converge on an automated process, so people who also want to write test pages, auditing harnesses, and/or automate testing itself will be encouraged to do so.

comment:17 Changed 7 years ago by mikeperry

Cc: runa added

comment:18 Changed 7 years ago by mikeperry

If technical people are looking for something to do, #5837 is something you can do right now to help us with build security, and learn some fun skills while you're at it.

comment:19 Changed 7 years ago by mikeperry

Ok everyone, we're starting to inch forward on this. If you're interested in participating, please email runa at torproject.org with the Operating System and CPU(s) you are able to test.

You may also want to read over https://lists.torproject.org/pipermail/tor-talk/2012-May/024286.html to get an idea of the larger plan here.

comment:20 Changed 7 years ago by Tichodroma

Cc: tichodroma@… removed

comment:21 Changed 7 years ago by Tichodroma

Cc: tichodroma@… added

comment:22 Changed 7 years ago by mikeperry

Owner: changed from erinn to runa
Status: newassigned

comment:23 Changed 7 years ago by mikeperry

Actual Points: 5
Keywords: MikePerry201205 added
Owner: changed from runa to mikeperry
Points: 5

Actually, I'm going to take this and close it for recordkeeping. I hope everyone has already emailed Runa.

comment:24 Changed 7 years ago by mikeperry

Resolution: fixed
Status: assignedclosed

comment:25 Changed 19 months ago by teor

Severity: Normal

Set all tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.