<div dir="ltr">On Fri, Jul 19, 2013 at 12:15 AM, Phill Whiteside <span dir="ltr"><<a href="mailto:PhillW@ubuntu.com" target="_blank">PhillW@ubuntu.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<div><br></div><div>just noticed on a recent bug report. I'd like to share my reply to it which I sent to social media (Well, PRISM has caused some ructions).</div>
<div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">And this an announcement, not an invite to another flame war... I've spent a lot of time trying to encourage chromum (not chrome) to be updated for those who choose to use it. One of the major tasks was for the security updates to be released regularly [done] and for the qa people to have access to the stable daily builds so we can test them before they get released. After a lot of work, and many months of discussions, chromium stable release is now available from a 'standard' (approved) area. So, in answer to those who thought myself, chad and Alex Shkop were sitting around doing nothing....</span><br style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">
<a href="https://launchpad.net/~chromium-daily/+archive/ppa" rel="nofollow nofollow" style="line-height:17px;color:rgb(59,89,152);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif;text-decoration:none" target="_blank">https://launchpad.net/<span style="display:inline-block"></span>~chromium-daily/+archive/ppa</a><div style="line-height:17px;padding-top:1px;color:rgb(51,51,51);width:16px;font-size:13px;margin-left:4px;display:inline-block;font-family:'lucida grande',tahoma,verdana,arial,sans-serif;min-height:16px;background-image:url(https://mail.google.com/mail/u/1/);background-repeat:no-repeat no-repeat">
</div><br style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif"><span style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">and here's the active one....</span><br style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">
<a href="https://launchpad.net/~chromium-daily/+archive/stable" rel="nofollow nofollow" style="line-height:17px;color:rgb(59,89,152);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif;text-decoration:none" target="_blank">https://launchpad.net/<span style="display:inline-block"></span>~chromium-daily/+archive/stable</a><div style="line-height:17px;padding-top:1px;color:rgb(51,51,51);width:16px;font-size:13px;margin-left:4px;display:inline-block;font-family:'lucida grande',tahoma,verdana,arial,sans-serif;min-height:16px;background-image:url(https://mail.google.com/mail/u/1/);background-repeat:no-repeat no-repeat">
</div><br style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif"><span style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">If you like testing, use the new ppa :)</span><br style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">
<span style="line-height:17px;color:rgb(51,51,51);font-size:13px;font-family:'lucida grande',tahoma,verdana,arial,sans-serif">As a foot note, I'd like to thank Alex for all the work he has done and also thank Chad for his un stinting work on getting chromium back up and running.</span></blockquote>
</div></blockquote><div><br></div><div><br></div><div>Hi all. I'm happy to keep chromium building and testable in a public place, but upstream releases come about every week, and between patch integration, ARMHF architecture build failures, ARMHF build time, and #security review and re-build, often the next release has arrived. People are already screaming for updates days before QA could even begin to test. I value assurance of quality, but I can't wait for long on human testing.</div>
<div><br></div><div>One thing I would like QA help with is automated tests. I've started some autopkgtest smoketest and build-time unit testing, but I'd like to have automated</div><div><br></div><div>- simple performance test</div>
<div>- UI translation test for languages that will be patched in from Launchpad soon (?!)</div><div>- integration test with webapps patches and extension<br></div><div>- learning what tests I didn't know to add to this list</div>
<div><br></div><div>I would love some patches or guidance.</div><div><br></div><div>lp:~chromium-team/chromium-browser/saucy-working</div><div><br></div><div><a href="http://www.chromium.org/developers/testing/browser-tests">http://www.chromium.org/developers/testing/browser-tests</a><br>
</div><div><br></div><div>- chad</div></div></div></div>