[09:14] <jamespage> jibel: thanks for raising that bug
[09:14] <jamespage> if you see any other Java errors like that please sub me to the bugs....
[09:23] <jibel> jamespage, yw. I will
[09:23] <jamespage> jibel, ta
[14:56] <jibel> jamespage, the script is buggy line 46 should be if title.lower() in testcase.title.lower()
[14:56] <jibel> then you can run it with
[14:56] <jibel> ./tracker_update_result -ad "Quantal Alpha 1" "Ubuntu Server EC2 EBS (Asia-Pacific-NorthEast) amd64" "User Data" ami-88bd0e89  Passed
[14:57] <jibel> and it works
[15:10] <czajkowski>  /c
[15:16] <smoser> where is 'tracker_update_result' live?
[15:17] <PaoloRotolo> Hi all!
[15:18] <smoser> jibel, ^
[15:19] <stgraber> smoser: http://paste.ubuntu.com/1028694/
[15:19] <stgraber> smoser: 14:56 < jibel> jamespage, the script is buggy line 46 should be if title.lower() in testcase.title.lower()
[15:20] <stgraber> smoser: 14:56 < jibel> then you can run it with
[15:20] <stgraber> smoser: 14:56 < jibel> ./tracker_update_result -ad "Quantal Alpha 1" "Ubuntu Server EC2 EBS (Asia-Pacific-NorthEast) amd64" "User Data" ami-88bd0e89  Passed
[15:20] <stgraber> smoser: 14:57 < jibel> and it works
[15:20] <smoser> stgraber, gracias.
[15:21] <jibel> smoser, https://code.launchpad.net/~jibel/+junk/qatracker
[15:21] <smoser> and thank you to you, jibel
[15:23] <jibel> smoser, you'll need bzr branch lp:~ubuntu-qa-website-devel/ubuntu-qa-website/python-qatracker
[15:23] <jibel> and setup your username and apikey
[15:23] <smoser> thanks.
[15:24] <jibel> hggdh, jamespage next step is to add a postbuild action in jenkins to report the result automatically after each run
[15:29] <balloons> ohh jibel fun script ;-)
[15:31] <jibel> balloons, definitely faster than clicking on tons of links :)
[15:32] <balloons> yes, but we could easily change the gui for reporting.. simple API interfaces are nice
[15:38] <stgraber> jibel, jamespage, balloons: note that because of the whole testcase management redesign that's going on, the get_testcases() API will change slightly for alpha2 and will require you to pass a series or milestone as the first parameter. This will likely break most existing scripts when it lands but I'll poke you again then.
[15:40] <balloons> stgraber, we need to meet again on that btw.. we missed this tuesday do to iso testing
[15:42] <stgraber> balloons: yeah, and I have a sprint next week :(
[15:42] <balloons> stgraber, ouch, when is it?
[15:42] <balloons> all week?
[15:42] <stgraber> balloons: virtual sprint, monday to wednesday, so we could reschedule for thursday or friday
[15:42] <stgraber> balloons: I'll try to get the remaining changes on my list (mostly UI stuff) done tomorrow
[15:43] <balloons> stgraber, ok.. the first call for testing is happening today using the staging site
[15:43] <balloons> I had a guniea pig (in addition to me) use it successfully
[15:44] <stgraber> ok, cool, so that should get us some feedback for the next call then
[15:44] <balloons> yea.. the biggest piece left UI wise for me is the bug reporting link
[15:45] <balloons> and perhaps help; but I don't think we mentioned that.. having a big question mark button to point people to help on using the page would be good to get at some point (link is easy, gotta work on the docs)
[15:50] <stgraber> yeah, once we have a good set of docs we can add a link ;)
[15:54] <phillw> balloons: https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview#Download_the_Alpha_1 has a couple of typos in it. It is refering to precise for kubuntu & lubuntu. Is it okay to edit them ready for release?
[15:54] <phillw> correction Edubuntu & Lubuntu :)
[15:54] <balloons> phillw, nice catch!
[15:55] <phillw> I'll go do it :)
[15:55] <balloons> skaet, note the above ^^
[15:55] <balloons> feel free to proofread for other typos phillw
[15:57] <phillw> balloons: kate gets notified of edits on that page :)
[15:58] <balloons> lol.. yes, I'm sure she does
[15:58] <jamespage> jibel: I'd actually prefer to make it part of the ec2 testing software
[15:58] <skaet> Thanks phillw,  please add any info you have on the features in Lubuntu.
[15:59] <jamespage> that way is someone runs one by hand manually it can still report to the tracker
[16:00] <jamespage> stgraber, how are the testcases for ec2 setup now?  I'd like to break them down a bit to match the tests execute in jenkins so its easier to report results.
[16:02] <stgraber> jamespage: that can certainly happen and will be even easier to manage once we have the testcase management branch merged (before alpha 2)
[16:02] <phillw> skaet: final decisions on the features have not yet been made. https://blueprints.launchpad.net/ubuntu/+spec/lubuntu-q-work-items has what is being discussed, but it seems a little unwieldly to include as a link in the A1 release notes?
[16:02] <stgraber> jamespage: I also remember talking to Ben about maybe reducing the number of products to the number of actual images being built and then have the various zones be testcases instead
[16:02] <stgraber> jamespage: so that we can add more zones without requiring new products (taking a lot of screen space on the tracker)
[16:03] <jamespage> stgraber, products == AMI's in this case?
[16:04] <skaet> phillw,  if you could just summarize the key things that have changed so far betwen precise and this Alpha 1 - that's all that's being looked for right now.
[16:04] <phillw> okies, I'll have a look through what has been ticked off as done!
[16:05] <stgraber> jamespage: yes, currently products == AMIs. We were discussing moving to products == whatever we build and then have the AMIs just be an implementation detail, and instead basically have something like "test build 20120607 in amazon eu-west-1", the test result would then contain what AMI was used
[16:06] <stgraber> jamespage: that'd reduce the number of entries on iso.qa.ubuntu.com by quite a bit and make it much more scalable when adding new providers/zones
[16:06] <jamespage> stgraber, sounds like it would work
[16:06] <jamespage> so long as I can index by BUILD and AMI that would work well
[16:08] <stgraber> I'll probably setup something like that on iso.qa.dev.stgraber.org and then have you, Ben and smoser look at it and see if that would work for you, but that'll have a to wait a couple of weeks...
[16:10] <balloons> stgraber, can you send me a list of lp usernames for folks who did quantal daily testing (since it's turned off right now, I can't use the site to get it)
[16:10] <stgraber> balloons: sure
[16:13] <xdatap1> Hi guys.
[16:13] <xdatap1> Quantal doesn't build anymore.
[16:13] <xdatap1> The following packages have unmet dependencies:
[16:13] <xdatap1>  poppler-data : Breaks: cmap-adobe-japan2 (<= 0+20090930-2)
[16:13] <xdatap1> is this known?
[16:14] <stgraber> yes
[16:15] <xdatap1> ok, no problem
[16:15] <xdatap1> bye
[16:23] <skaet> thanks phillw.   ( updates in TechnicalOverview)
[16:24] <phillw> There's a lot "in the works", A1 is early days for us :)
[16:25] <skaet> :)
[18:57] <phillw> skaet: is it too late to update the TechnicalOverview? One of the PPC testers would like to ammend the note regarding the Ffox issue to add that it can be manually installed.
[18:57] <skaet> phillw,  go ahead,  its at QuantalQuetzal/TechnicalOverview/Alpha1 now though.
[20:14] <phillw> balloons: ping
[20:15] <balloons> phillw, pong
[20:15] <phillw> have you got a few minutes for a chat?
[20:15] <balloons> sure thing
[20:16] <phillw> I'm a bit puzzled that https://wiki.ubuntu.com/QuantalQuetzal/TechnicalOverview/Alpha1 is sending people to ,in our case, http://cdimage.ubuntu.com/lubuntu/releases/quantal/alpha-1/ instead of the iso-tracker having  the Alpha1 as milestone release as happened last cycle?
[20:18] <balloons> phillw, must be a long day for me.. I'm confused :-)
[20:18] <balloons> can you clarify?
[20:19] <phillw> he he, I know that feeling.
[20:19] <phillw> http://iso.qa.ubuntu.com/qatracker used to show the milestone and daily images for 12.04
[20:20] <balloons> k, following you there
[20:20] <phillw> So, at this stage, A1 would be status 'released' and then the dailies would re-appear as 'testing'?
[20:20] <balloons> yes, also agree
[20:20] <phillw> it doesn't :)
[20:21] <balloons> phillw, it's been an hour since release, I think everyone is taking a breath.. but that is also my expectation
[20:21] <balloons> it may not change I suppose until tomorrow with the new dailies? I don't think i've ever watched that closely
[20:21] <phillw> okies, no worries :) Just disn't want to miss up on a potential new tester :P
[20:22] <phillw> s/disn't/didn't
[20:22] <balloons> yes, I agree..
[20:22] <jibel> phillw, reload http://iso.qa.ubuntu.com/qatracker
[20:22] <jibel> feeling better :)
[20:23] <jibel> ?
[20:23] <phillw> jibel: yup, but what about the tech notes, in that case?
[20:24] <balloons> jibel, :-)
[20:24] <phillw> I know this is a what came 1st .. chicken or egg, but iso-tracker is a better place for people to view what is going on?
[20:24] <balloons> phillw, lol -- http://www.lastfm.de/passwordsecurity
[20:24] <jibel> phillw, I don't understand what's wrong with the tech notes, it's linked to the images that have been released
[20:25] <jibel> doesn't http://cdimage.ubuntu.com/lubuntu/releases/quantal/alpha-1/ contains the right images for a1 ?
[20:26] <phillw> jibel: yes it does. What I meant was rather than have a very long release note, the bugs affecting each iso are noted against them on the tracker.
[20:27] <Claudinux> hi there, I would like to know if the Mythbuntu team confirmed future releases only for LTS
[20:29] <phillw> any person using the tracker will also benifit from clicking on the bug and getting it's absolute current status?
[20:29] <jibel> phillw, understood. maybe a link back to the tracker could be added to the release notes for people interested into details. skaet will be happy to talk with you about improvement of the release notes
[20:29] <phillw> np. It is just a thought :)
[20:31] <balloons> Claudinux, you should ask on #mythbuntu, however I believe that is correct
[20:32] <balloons> phillw, ok, so how would the notes be different. I feel slow on this
[20:32] <stgraber> Claudinux: still being discussed with the TB
[20:33] <balloons> it sounds like your wanting to change the tracker, not the notes
[20:33] <phillw> balloons: I've got a couple of ideas to bounce around. but the time for that is not just after the sprint for a milestone :)
[20:33] <phillw> balloons: nope, it is the notes.
[20:37] <jibel> balloons, the point is that release notes are static, while the tracker is dynamic, have the current status of the bugs and more details
[20:37] <balloons> jibel, light-bulb on!
[20:37] <balloons> thank you
[20:38] <Claudinux> ok, thanks for feedback balloons & stgraber :-)
[20:39] <jibel> well, enough quantal for today, good night everyone
[20:39]  * jibel -> bed 
[20:40] <skaet> Thanks jibel!   Sleep well.
[22:21] <nm_geo> are the latest daily spins dated correctly?