[tor-qa] Stable TBB QA v2.2.37-2

[Colin C.]

Testing: tor-browser-gnu-linux-x86_64-2.2.37-2-dev-en-US.tar.gz
Platform: Fedora 17
Processor: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz

TBB Launches successfully - OK
Connects to the Tor network - OK
Browser toolbars and menus work. Tab dragging works. - OK
DNS - No leaks observed (wireshark)

All extensions are present and functional -  OK
 - HTTPS-Everywhere 2.0.5
 - NoScript 2.4.8
 - TorButton 1.4.6

WebBrowsing works as expected - OK
 - HTTP, HTTPS, .onion browsing works
 - HTML5 videos work
 - ip-check.info - OK
 - samy.pl/evercookie - OK (new identity clears cookie)
 - html5demos.com/web-socket - Not Connected / Socket Closed

On Thu, Jul 26, 2012 at 1:15 AM, Mike Perry <mikeperry at torproject.org>wrote:

> I am standing in for Runa as the announcer this week, but with any luck
> we can replace these announcement mails with a script soon enough.
>
> We have two TBB releases today: a stable and an alpha. Be sure to limit
> replies in this thread to reports on the stable series. We want to get
> the stable release out ASAP (within about 24 hours). An alpha post will
> follow shortly, and it will be given more time for feedback (let's say
> 60 hours). Please test the alpha more thoroughly, but also please
> prioritize the stable release to make sure it is at least functional.
>
> If you decide to test both releases, please reply to each thread
> individually. If you have additional comments or concerns about the
> process or test urls, please start new threads rather than reply here.
>
> The stable bundles update Firefox to 10.0.6esr, Vidalia to 0.2.20, and
> NoScript to 2.4.8. Please see Docs/changelog in the bundles for details.
>
> You can find the stable bundles themselves for Linux, Mac OSX, and
> Windows at: https://people.torproject.org/~erinn/qa/stable/
>
> Linux users: As you know, life is always hard for you, but that's ok
> because it makes you stronger; make sure you get the 2.2.37-2 version,
> not the stale 2.2.37-1 version.
>
> Also note: We are short on Windows testers, especially those with wacky
> AV software. If that's you, we would love to hear your input for at
> least one of the two releases.
>
> You have until July 27th 2012 06:00 UTC to test and report back. Please
> email this list directly with results or if you have any questions. Keep
> in mind that an email saying "I tested TBB on Debian Wheezy and found no
> bugs" is just as useful as a list of issues. I think my own personal
> favorite response format so far was:
> https://lists.torproject.org/pipermail/tor-qa/2012-June/000004.html but
> as always feel free to innovate and improve on that. Note: I'm pretty
> sure we don't need your specific CPU string, only x86 vs x64.
>
> For testing ideas, see the BuildSignoff wiki page and the TBB design
> document for information about different types of tests you can perform:
>
> https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff#DocumentationChecklist
> https://www.torproject.org/projects/torbrowser/design/#Testing
>
>
>
> Thank you for helping us make the Tor Browser Bundle better. Again,
> please don't hesitate to email if you have questions. If you have any
> suggestions on things we can do better, please let me know.
>
>
> Thanks!
>
>
> --
> Mike Perry
>
> _______________________________________________
> tor-qa mailing list
> tor-qa at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
>
>


-- 
- Phoul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-qa/attachments/20120726/ca8571e8/attachment.html>