<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> Ok, so we're a bit delayed in starting this because, well, there was a Holiday in North America called Thanksgiving. Forgive me. :-p So, this week (through Saturday) is our first cadence week. What that means is we will be focusing testing specific packages (or isos) during the week. What you can do to help is to run through a testcase (or a few :-) ) at some point during the next week and report your results. The goal here is NOT to make all the tests green everyday. Instead, we want to test on a deeper level and really look for bugs in the software (or even the testcases :-) ) so we can be confident in the health of the package(s) we are testing. To that end, there is no daily target -- rather we want to test through Saturday (whenever that is in your localtime ;-) ). Think quality, not quantity (I know, it's a bad pun.. quality quality...) What this means practically is during the next week, try to execute some testcases for our week 1 targets (which are libreoffice, unity autopilot tests and the daily raring iso). You can find the wiki page detailing this here: <a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week1">https://wiki.ubuntu.com/QATeam/Cadence/Raring/Week1</a> The master schedule can be found here: <a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/QATeam/Cadence/Raring">https://wiki.ubuntu.com/QATeam/Cadence/Raring</a> Again, I would suggest finding a day and time that works for you and adding your results. Feel free to use IRC (#ubuntu-quality on freenode) or this mailing list to discuss any bugs you may find. At the end of the week, I'll recap what we did (bugs, tests ran, etc), and we can evaluate the results to see if further followup and focus is needed or not. Now, our testing focus's each week will change in order to target packages that need more QA work, or new packages that recently landed in QA. Now, this week I will also be posting the next bits in our autopilot series -- intending to teach you about running and writing autopilot testcases. Our cadence testing this cycle will include running both automated and manual tests -- we need both ;-) You'll note the autopilot unity testsuite is included this week. I hope our subsequent testing weeks can feature some new automated autopilot tests written by some of you :-) If writing automated tests aren't up your alley, don't worry we need manual testcases too! Happy Testing everyone, Nicholas </body> </html>