=== cprofitt_ is now known as cprofitt
=== zul_ is now known as zul
[13:40] <airk> Topic typo? Should it not be 11.04.02?
[14:25] <jibel> primes2h, hi,
[14:26] <jibel> primes2h, I reviewed the fix, here is the laptop summary I get with the testing dataset http://paste.ubuntu.com/578357/
[14:26] <jibel> primes2h, looks good
[14:27] <jibel> but it would probably have been easier to generate the report with on single sql query and relying on the active milestone rather than splitting the milestone name.
[14:27] <jibel> but well, that's lot of changes for little benefit.
[14:28] <primes2h> Hey jibel:
[14:30] <primes2h> jibel: you mean the single laptop report page?
[14:32] <primes2h> jibel: like this one? http://laptop.qa.ubuntu.com/qatracker/laptop/Natty/28034
[14:33] <jibel> primes2h, I mean the laptop summary page: http://laptop.qa.ubuntu.com/qatracker/laptop
[14:35] <jibel> there is code like $releasename=substr($milestone->title,0,strpos($milestone->title," "));
[14:35] <jibel> pushed to an array
[14:35] <jibel> the used to do a like and find the milestone back
[14:35] <jibel> but nevermind.
[14:36] <primes2h> jibel: in fact, I needed to do that because I want that milestones about final releases (e.g. Lucid or Natty when ready)  stay on the tracker together with active dev milestone.
[14:38] <jibel> oh okay.
[14:38] <primes2h> jibel: so in that table you'll have, e.g,  Lucid (referred to final release) and Natty  (Beta1)
[14:39] <primes2h> jibel: in fact you can use the tracker to test final releases also.
[14:39] <primes2h> and all (stable and dev) are reported on the summary
[14:40] <jibel> primes2h, understood
[14:41] <jibel> primes2h, any other fix, typo, comments, complaints ... before I merge it ? ;-)
[14:41] <primes2h> jibel: the fix about last bug is just a line, when I tested locally I hadn't so much data reported about ISO tracker so I didn't catch it.
[14:42] <jibel> primes2h, same here I'm so used to see all the releases at once that I didn't see it.
[14:43] <primes2h> jibel: we are starting to test the tracker itself within our Italian testing group, I was wondering if it is worth opening to whole testing team
[14:45] <primes2h> Beta milestone is coming in 3 week and time is not so much.
[14:46] <primes2h> I mean "beta 1"
[14:46] <primes2h> s/week/weeks
[14:49] <primes2h> Moreover, we are also thinking about creating a LP laptop team with a dedicated ML in time for the announce of the new tracker. What do you think?
[14:50] <primes2h> jibel: I mean "LP laptop testing team"
[15:06] <primes2h> jibel: about other fix, typo ecc., I think it should be ok now, but it's probably better to wait 2/3 days of testing in case we face other issues
[15:56] <jibel> primes2h, sorry, was on the phone.
[16:09] <primes2h> jibel: n.p.
[16:18] <jibel> primes2h, a laptop testing team on launchpad and opening the tracker to a wider community is a good idea.
[16:19] <jibel> primes2h, the fixes will be online early next week, starting from there we can start announcing the availability of the tracker.
[16:25] <primes2h> jibel: about opening to a wider community I was talking about testing the tracker itself for 2/3 days to find bugs in it, but in fact there is not much time left I see.
[16:27] <primes2h> jibel: Tests done by our group should be enough.
[16:28] <primes2h> jibel: there is already one done and seems to be ok.
[16:28] <primes2h> http://laptop.qa.ubuntu.com/qatracker/laptop/Natty/28034
[16:31] <primes2h> jibel: just to explain better, the table you find in the report is intended to keep track of all milestone tested, one for column.
[16:38] <charlie-tca> jibel: Can we have the screen-reader install on the tracker for the beta1
[16:38] <charlie-tca> ?
[16:38] <primes2h> jibel: as follow: http://img845.imageshack.us/i/schermatai.png/
[16:50] <primes2h> jibel: ok about LP team and ML, I'll go on, thank you.
[16:51] <jibel> primes2h, thanks to you. I did the merge but didn't request the publication to the server, let me now when you think you've received enough feedback.
[16:56] <jibel> charlie-tca, sure, can you file a bug against the project ubuntu-qa-website and assign it to me. Indicate which products you want to add this test case to.
[16:56] <primes2h> jibel: just a last thing. after testing the tracker itself, the fake milestone needs to be deleted, not just hidden, otherwise it appears on the report. That's because I had just 3 milestone status to choose about that, testing, released and hidden.
[16:57] <charlie-tca> jibel: thanks, will do
[16:58] <primes2h> so I needed to have a milestone that wasn't on the tracker (e.g. Alpha 1) when testing Alpha 2 but that would appear in the report
[16:59] <jibel> primes2h, ack.
[16:59] <primes2h> Hidden status is the only one that fit this need
[17:24] <primes2h> jibel: a last thing, what about a dedicated ML along with LP team? is it worth or it's better to rely on ubuntu-qa ML?
[17:26] <primes2h> jibel: this is "really" the last thing for today, sorry for boring you ;-)
[17:27] <jibel> primes2h, np :)
[17:27] <jibel> primes2h, the advantage of relying on ubuntu-qa is that you'll directly benefits of the subscribers to this ML
[17:27] <primes2h> jibel: I agree.
[17:30] <primes2h> jibel: can I specify the LP team as a part of the ubuntu-qa in the description?
[17:31] <primes2h> I mean as an official project
[17:31] <primes2h> and link it in some way to ubuntu-testing
[17:33] <primes2h> mmh, I could add it as a team in the Ubuntu Testing Team itself
[17:40] <jibel> primes2h, it was discussed and accepted at UDS, so it's already an official project part of the Ubuntu testing effort. Now the laptop testing team should be a subteam of the broader Ubuntu testing team. ubuntu-qa includes QA activities as a whole, not only testing.
[17:43] <primes2h> jibel: sure, thanks for the confimation. :-)