[06:44] <Fableflame> Hello, I'm new here.
[08:41] <alourie> good morning
[08:45] <Fableflame> Hello
[08:56] <jibel> good morning
[08:56] <jibel> mvo, just to avoid overlap, I'm investigating the lts-server upgrade failure
[08:56] <jibel> and will file a bug
[09:10] <Fableflame> What's up?
[09:12] <brendand> gema - if we create wiki pages to cover the work we do for the QA tasks, should they go under QATeam on the Ubuntu wiki?
[09:24] <mvo> jibel: thanks
[09:28] <Fableflame> So how complicated is it, helping ubuntu-testing?
[09:29] <brendand> Fableflame - it depends what you want to do
[09:29] <brendand> Fableflame - do you already participate in ISO testing?
[09:48] <Fableflame> brendand, No, I've kind of just gained interest in helping out.
[09:55] <Fableflame> brendand, welcome back
[10:11] <Fableflame> brendand, you having connection issues?
[10:11] <brendand> Fableflame - i'm alright, just flicking between systems
[10:18] <Fableflame> ah
[10:25] <Fableflame> So, how complicated is ISO testing?
[10:27] <brendand> Fableflame - ISO testing is straightforward
[10:27] <brendand> Fableflame - It's only done at certain release points though. Alpha 1 was just finished last week
[10:28] <Fableflame> Then what about testing daily builds? That's smoke testing, right?
[10:43] <brendand> Fableflame - technically, no
[10:44] <brendand> Fableflame - you can test the daily images if you like, but have you seen the mail on the ubuntu-qa mailing list?
[10:44] <Fableflame> No, I haven't joined any mailing lists yet.
[10:45] <brendand> Fableflame - ok. https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
[10:45] <Fableflame> I just decided that I wanted to be a part of this a couple of hours ago
[10:57] <Fableflame> Looking at the last message that was posted, I don't know if there is anything there that I can do.
[10:58] <Fableflame> Maybe I should re-read it
[11:02] <brendand> Fableflame - next ISO testing is the start of February
[11:02] <brendand> Fableflame - if you have a spare system you can run alpha1 on and keep updating, then report bugs if you find issues
[11:03] <Fableflame> brendand, using it on my main system actually won't be a problem, I don't use it for anything important, really.
[11:05] <brendand> Fableflame - ok. bear in mind it can be unstable (hopefully not but no guarantees)
[11:09] <Fableflame> brendand, will do. The only thing I use this laptop for is facebook and email. I keep windows on my desktop for Steam.
[11:11] <Fableflame> brendand, also when I install the alpha1, should I just stick to using the apps that come with it, or should I install the apps that I normally use? Like I use Gnome3 instead of Unity on this install.
[11:12] <brendand> Fableflame - to be honest, unity bugs will be much more useful than gnome-shell bugs, but who am I to tell you what to use
[11:12] <Fableflame> brendand, that's kind of what I was thinking, what with everybody constantly complaining about Unity. I don't dislike it, I just prefer Gnome.
[11:13] <Fableflame> but I can stick with Unity for testing's sake
[11:22] <Fableflame> brendand, has anybody gotten back to you about testing apt yet? Because that sounds like something simple enough that I could handle.
[11:23] <brendand> Fableflame - well, this is more in the context of testing it automatically on a regular basis. i wouldn't imagine it would be worth someone doing manually with every build
[11:24] <Fableflame> brendand, oh. You'll have to forgive me. I'm hoping this gets easier the longer I'm around.
[11:25] <Fableflame> I've never contributed to a project like this before
[12:45] <Fableflame> Hey
[12:45] <Fableflame> Is 12.04 supposed to look exactly like 11.10 at this point? The background on the log in screen even still says 11.10.
[13:19] <patdk-wk> yes
[13:19] <patdk-wk> I don't think that stuff changes till beta
[13:21] <jibel> Fableflame, that is bug 892394
[13:21] <ubot4> Launchpad bug 892394 in unity-greeter (Ubuntu Precise) (and 2 other projects) "Greeter logo needs to be updated for 12.04 (affects: 2) (dups: 1) (heat: 16)" [Medium,Triaged] https://launchpad.net/bugs/892394
[13:26] <Fableflame> jibel, oh okay
[13:27] <jibel> yw
[13:28] <Fableflame> jibel, yeah, thanks.
[13:28] <Fableflame> I need to make a launchpad account
[14:20] <Fableflame> So once I'm all registered with Launchpad, should I start doing Test Cases?
[15:27] <alourie> hello again
[16:21] <stgraber> skaet, jibel, Daviey, utlemming: Working API to push results to the ISO tracker, just replace my login by yours and blablabla by the API key you set in User profile: http://paste.ubuntu.com/761764/
[16:22] <utlemming> stgraber: awesome, thank you kindly
[16:22] <stgraber> I'd suggest setting up separate accounts (local drupal accounts) for thins like Jenkins (like we have for our ubuntu-cdimage account)
[16:22] <stgraber> API currently only allows pushing results, I'm finishing testing the one for updates, listing results and removing results
[16:22] <skaet> stgraber: *\o/*  thanks!!!
[16:23]  * skaet starts to look forward to seeing the results showing up
[16:23] <jibel> congrats stgraber that's great
[16:24] <stgraber> doh, just noticed I missed something kind of important in the API, linking bugs ...
[16:24] <alourie> does this mean possibly external apps for tracking?
[16:24] <stgraber> will post an updated python script in a few minutes with the updated API call (I'll add bugs and critical_bugs, both being lists of ints)
[16:24] <alourie> s/tracking/iso testing/ ?
[16:29] <stgraber> jibel, utlemming, Daviey: http://paste.ubuntu.com/761775/
[16:29] <stgraber> updated to include an extra "bugs" parameter which is a dictionary of bugnumber (bugnumber string) => bugimportance (0 = regular, 1 = critical)
[16:35] <stgraber> alourie: yep, with the API you can do most of what's available on the website (at least once it's complete), so the initial use is for automated testing, but someone could also have checkbox or something else push results directly
[16:44] <alourie> stgraber: I thought actually about, maybe, more "single-task" applet, such as application with indicator. A participant would get, say, notification "There's a test available for you. Would you mind running it?", then person says yes, runs the test according to instructions, and reports the result right there.
[16:45] <alourie> no website, login each time, etc
[17:41] <stgraber> alourie: definitely doable, would just need to export the subscriptions API too so the indicator can query what the user subscribed too, the rest is already possible with the current API
[21:20] <alourie> gema: ping
[21:23] <gema> alourie: pong
[21:29] <alourie> gema: I may not be able to make the meeting tomorrow
[21:30] <gema> alourie: ok, no worries, I will send a link to the logs to the list
[21:30] <gema> alourie: if you have any update, you can send it to me whenever you can
[21:30] <alourie> so I'll read the logs later, and whichever you decide - I'll probably take it offline
[21:30] <alourie> :-)
[21:30] <alourie> sure
[21:30] <alourie> thanks
[21:30] <gema> alourie: thank you :)
[21:31] <gema> alourie: we won't give you any extra tasks, no worries :D
[21:38] <alourie> gema: I have no problems with extra tasks :-)
[21:39] <gema> alourie: haha, no tasks for no present people, that's the rule, you can send any comments/questions/progress on your current tasks to the list
[21:39] <gema> alourie: I am really excited with so many collaborators
[21:39] <alourie> yea
[21:39] <alourie> it's been awhile since it was like that
[21:40] <alourie> it's been quiet area in community QA for some time
[21:40] <gema> yep
[21:40] <alourie> I want to PR it now
[21:40] <gema> go for it
[21:41] <alourie> I am
[21:41] <alourie> :-)
[21:41] <gema> :)
[21:41] <alourie> need a bit more time
[21:41] <alourie> but I'll get there
[21:41] <gema> yep, I feel quite overwhelmed too, but getting there
[21:41] <Fableflame> Has anyone had the Update Manager freeze up on you?
[21:42] <alourie> Fableflame: no, not really
[21:42] <gema> Fableflame: me neither
[21:42] <Fableflame> After clicking "Install Updates" it just kinda greys out and sits there.
[21:42] <gema> Fableflame: which version are you using?
[21:43] <Fableflame> 12.04
[21:43] <gema> I have been told that A1 has problems with the updates, so maybe you are seeing a version of that problem
[21:43] <Fableflame> ah
[21:43] <gema> but I am not sure, jibel is your man, when he is online, tomorrow
[21:43] <gema> or maybe hggdh has seen it too
[21:44] <Fableflame> It just came back, didn't install anything. I tried again and it's doing the same thing O.o
[21:44] <gema> sorry I have to leave for today, talk to you tomorrow
[21:45] <Fableflame> Yup, there is already a bug filed. https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/894671
[21:45] <ubot4> Launchpad bug 894671 in update-manager (Ubuntu) "update-manager freezes after initialization (affects: 3) (heat: 31)" [Undecided,Confirmed]
[21:45] <alourie> Fableflame: I have it crashing a lot, so I do it manually
[21:46] <alourie> s/it crashing/update manager crashing/
[21:46] <Fableflame> the command for apt is apt-get update, right?
[21:47] <alourie> yes
[21:47] <alourie> that will fetch the updates
[21:47] <alourie> and then 'upgrade' will actually do the upgrade
[21:47] <roadmr> Fableflame: usually apt-get update (updates the packages lists), followed by either apt-get upgrade (apply available updates) or apt-get install foo (install just package foo plus its dependencies)
[21:48] <Fableflame> thanks guys
[21:48] <alourie> yea, what roadmr said :-)
[21:49] <Fableflame> What's foo? Sorry, I'm kind of a noob.
[21:49] <alourie> Fableflame: it's a generic name for a package, not anything specifiv
[21:49] <Fableflame> oh haha
[21:49] <alourie> just an example
[21:50] <alourie> you'll see it  used a lot around code examples
[21:50] <roadmr> sorry, should have clarified on that :)
[21:51] <Fableflame> No problem. I should probably be a little more informed before I attempt helping out with testing.
[21:54] <roadmr> Fableflame: all help is appreciated, and nobody was born knowing everything, so asking is ok
[21:55] <Fableflame> roadmr, thanks. So far people here seem pretty friendly.
[21:59] <alourie> Fableflame: well, you've just started. We're going to be much worse later.
[21:59] <Fableflame> haha
[22:00] <alourie> don't worry, just be patient. Sometimes, you won't get answers right away, as noone would be awake to do so.
[22:04] <Fableflame> I can't seem to find the list of bugs.
[22:08] <Fableflame> Found it
[22:10] <Fableflame> Are there no open bugs for Ubuntu Testing Team?
[22:11] <Fableflame> Or do we just file our bugs with the rest of Ubuntu?
[22:14] <alourie> Fableflame: what do you mean? filing and triaging bugs are 2 tasks within the QA team.
[22:14] <alourie> testing is another task
[22:15] <Fableflame> oh
[22:15] <alourie> actually, filing bugs is not just /our/ task, it's everyones'
[22:15] <alourie> :-)
[22:15] <Fableflame> So what do I do if I come across something that doesn't work right?
[22:15] <alourie> file a bug, of course
[22:16] <alourie> if you're sure it's a bug
[22:24] <Fableflame> Where do I file bugs at? I don't want to accidentally file them in the wrong place.
[22:26] <roadmr> Fableflame: someone will look at them for triaging after you file them, so it's not too bad if you file them in a wrong place
[22:27] <roadmr> Fableflame: best way to file a bug is from within ubuntu, open a terminal and type ubuntu-bug package
[22:27] <roadmr> Fableflame: where package is the one where you found the bug
[22:27] <Fableflame> oh ok
[22:27] <roadmr> Fableflame: for instance ubuntu-bug firefox
[22:27] <roadmr> Fableflame: if later it turns out that the problem was in Flash rather than in firefox, a triager and/or developer will figure it out and change it
[22:28] <roadmr> Fableflame: the advantage to using ubuntu-bug is that it adds a bunch of debugging information, such as hardware data, software versions, and so on
[22:28] <Fableflame> oh okay
[22:29] <Fableflame> Do I need to set up my SSH key first? I just finished setting up my PGP.
[22:29] <roadmr> Fableflame: not necessarily, you can file bugs without having configured the SSH key
[22:30] <Fableflame> ok
[22:30] <Fableflame> brb, gotta reboot