=== tumbleweed_ is now known as tumbleweed === Myrtti_ is now known as Myrtti === Myrtti is now known as Guest71494 === yofel_ is now known as yofel === matt_symes is now known as Guest48735 === myrtti is now known as Myrtti === popey_ is now known as popey === dannf` is now known as dannf [15:00] o/ [15:00] hey [15:00] hiya [15:01] #startmeeting [15:01] Meeting started Fri May 25 15:01:05 2012 UTC. The chair is skaet. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:01] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [15:01] yo [15:01] Welcome to the first of our weekly release meetings for the Quantal cycle! [15:01] Before the meeting, you can find the next meeting's agenda at: https://wiki.ubuntu.com/ReleaseTeam/Meeting/Agenda (this meeting's conventions and format are documented there). [15:01] After the meeting, there will be the hot links to the teams status, summary pages, etc, and the wiki page will remain available with links to the IRC logs at: https://wiki.ubuntu.com/ReleaseTeamMeeting/2012-05-25 (where YYYY-MM-DD will change based on the meeting ;) ) [15:01] . [15:01] hello [15:01] hi [15:01] can I have the floor [15:02] Star2012, there will be an open Q&A session announced as the topic soon. [15:02] Before we go into the open Q&A session, just want to give a reminder of some other key links. [15:02] 12.10 Draft Schedule: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule [15:02] 12.10 Team Interlock: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock [15:02] 12.04.1 Schedule: https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule [15:02] . [15:02] ty [15:02] Key events: [15:02] 2012/05/31 - FeatureDefinitionFreeze (all blueprints should be in and approved for Quantal/12.04.1) [15:02] 2012/05/31 - Reset of trendline on http://status.ubuntu.com/ubuntu-quantal/ [15:02] 2012/06/07 - Alpha 1 Milestone Release (soft freeze on 06/04) [15:02] 2012/06/21 - DebianImportFreeze [15:02] . [15:03] (yes A1 is coming up very soon.... ;) ) [15:03] yay [15:03] Conventions to use: 'o/' if you want to ask a new question after the current conversation is finished. Please use '..' when you've finished discussion so that we can move on to next question promptly. :) [15:03] . [15:03] Here are the weekly team updates received: [15:03] Hardware Cert: ara, https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001252.html [15:03] Ubuntu Desktop: seb128, https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001253.html [15:03] Lubuntu: gilir, https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001255.html [15:03] Edubuntu: stgraber, https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001256.html [15:03] UbuntuOne: joshuahoover: https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001257.html [15:03] Kernel: ogasawara: https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001259.html [15:03] Security: mdeslaurs: https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001260.html [15:03] QA: jibel: https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001264.html [15:03] Server: arosales https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001265.html [15:04] Xubuntu: astraljava https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001266.html [15:04] Linaro: https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001268.html [15:04] Unity: dbarth, https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001269.html [15:04] Kubuntu: ScottK, https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001270.html [15:04] Thank you to those folk that got their ones in by 1900 UTC on 5/24! :) [15:04] and I think that takes care of the preliminaries.... :) [15:04] .. [15:04] *sniff* sorry [15:04] lol :) [15:04] Foundations: ogra https://lists.ubuntu.com/archives/ubuntu-release/2012-May/001272.html [15:04] (to complete it) [15:04] .. [15:05] Thanks ogra_ :) [15:05] #topic Open Comment, Question and Answer section... === meetingology changed the topic of #ubuntu-meeting to: Open Comment, Question and Answer section... [15:05] ty [15:05] il take the floor for 1 min plz [15:05] Star2012, go [15:05] ok issue ##Hardware [15:06] user adie AKA incest-adie [15:06] 1sec [15:06] erm [15:06] the uset is now also in ##Ubuntu-ops [15:06] Nothing to do with this meeting. Please go elsewhere. [15:07] Star2012, this doesn't appear relevant to this meeting. [15:07] ive warnrd the user and the channel ops not to let the user use this nick on this network [15:07] well its a server user issue [15:07] who sould i talk to [15:07] should [15:07] its a freenode/IRC issue [15:07] talk to the IRC Ops team [15:07] what channel [15:08] skaet, sorry [15:08] https://wiki.ubuntu.com/IRC/IrcCouncil [15:08] Star2012, lets figure this out, in sideband discussion. [15:08] ty [15:09] * skaet move on back to our regularly scheduled release issues ;) [15:09] sorry [15:09] based on interlock, we want to adjust alpha 3 to July 26 (currently August Any one see problems about adjusting A3 to one week earlier? [15:10] no issues here that i can see. [15:10] arosales, ogra_, seb128, ScottK, and others interested ^? [15:10] thanks Daviey :) [15:10] hmm [15:10] none from me [15:10] I see it as a good thing [15:10] WFM [15:10] one moment [15:10] It seems OK for Kubuntu. [15:10] We miss KDE SC 4.9.0 either way. [15:10] no issue from the desktop side [15:11] should be fine, though note that we will change the arm images to live, that might cause unexpected breakage [15:11] skaet: So, Openstack upstream has done a pretty good job of aligning with out release schedule [15:11] http://wiki.openstack.org/FolsomReleaseSchedule [15:11] (and might require extra fixes and rebuilds) [15:11] ty for your time [15:11] ogra_, fair enough. [15:12] skaet: So, moving it one week earlier, means we don't get Folsom-3 [15:12] oh, wait, that was A3 ... we should have switched by then, ignore my comment :) [15:12] Daivey, can we see if they can adjust? QA is going to be slammed with 12.04.1 in August, so trying to cut them some breathing room. [15:13] skaet: Hmm.. Can we hold off deciding this right now? [15:13] Daviey, yes, [15:13] super [15:14] want to close it early next week before planning freeze though. :) [15:14] .. [15:14] Need to make some adjustments on status.ubuntu.com to get it more efficient again. [15:14] It still appears to be tracking workitems from Oneiric and Precise. Which is making the http://status.ubuntu.com/ubuntu-precise/ rather misleading in terms of trend lines, to put it mildly. :P [15:14] Any one have concerns about turning the tracking off for Oneiric and Precise ? [15:14] (I still want the graphs and last snapshot of data visible though, useful for trending information ;). [15:15] skaet, we should have turned them off at release [15:15] seb128, I think so too. [15:15] skaet, precise is completly screwed now because we carried specs over to q and they drop off the precise charts [15:16] skaet, I was trying to look at how many workitems desktop team got done in precise this week but we lost those infos [15:16] most of the items just got dropped from it [15:16] yes - if no one has strong concern otherwise - I'll work to see if we can get the data rolled back for precise to when we released [15:16] and freeze it there [15:16] skaet, I think pitti also raised concerns about the time it takes to generate the graphs over several releases [15:17] seb128, yup. and cjohnston is concerned as well, and it serves no useful purpose from what I can tell, so lets fix it. [15:17] :) [15:17] ;-) [15:18] but I wanted to make sure that everyone knew about it, and there wasn't something we were overlooking. [15:18] :) [15:18] given no other comments, I'll move forward with figuring out how to get this cleaned up. [15:18] .. [15:19] * skaet has a long list of questions, but wonders if anyone else wants to ask some? [15:19] ogasawara, with the transition to debian unstable occurring there's going to be a lot of churn for the next couple of weeks, can we hold off on move over to v3.5-rc1 kernel until after Alpha 1? [15:19] skaet: I think that should be do-able [15:20] thanks ogasawara. *whew* [15:20] .. [15:21] (sorry, should have waited for ogasawara ".." ) [15:21] .. [15:21] :) [15:21] ogra, any feeling on when we'll be getting arm daily images again? what's the cause of the breakage? [15:22] ogra_, ^ [15:23] skaet, broken chroots on the livefs builders, afaik infinity is on it [15:23] ogra_, will we be trying for arm images for A1? [15:24] s/broken/out7 [15:24] grr [15:24] *outdated [15:24] why does IRC swallow my typing :P [15:24] I got the impression nonexistent was more like it, but either way ... [15:25] skaet, i would like to see arm A1 images, yes, but given we will switch flash-kernel to the new world order and at the same time switch to live installs it might be a bit bumpy [15:25] ogra_, ok, we'll keep it in the "try for" list, but not block on it. [15:25] yeah, sounds sane [15:26] .. [15:26] ScottK, based on your blueprints you'll be trimming down the images for kubuntu this cycle. What is the rollout plans for that? which images do you want to try for with A1? [15:27] skaet: I don't know. [15:28] ScottK, can we figure it out by next week? [15:28] Sure. [15:28] thanks. :) [15:28] .. [15:28] The short answer for an Alpha 1 is something like 'the ones that will build' anyway. [15:29] * ogra_ always thought they are "the ones that install" [15:29] fair 'nuf. it is A1 after all. Just like to start pruning images down as soon as possible. :) [15:30] Side note, For Alpha1, Server would like to switch to squashfs based images, rather than pool of deb's... Perhaps releasing both style images for A1 for early comparison. [15:30] I'm thinking of the testing side of it, and trying to make sure we've got folks focused on what we really care about. [15:31] Daviey, interesting side note, thanks for raising. Was coming to server later. Lets discuss in #ubuntu-release after the meeting. [15:31] Daviey: You're not going to use D-I anymore? [15:32] * skaet wondering about naming, dailies, etc. as well during experiment. [15:32] ScottK: no, still using d-i [15:32] OK. I didn't know that was possible. [15:32] just using a squashfs instead of a pool [15:33] .. ;) (discussion to go to #ubuntu-release) [15:33] seb128, which Ubuntu desktop images make sense to produce and test? oversize desktop and alternate? can we drop DVD from the dailies? [15:34] isnt alternate dead ? [15:34] ogra_ that's what I'm trying to figure out, not got enough data from blueprints status yet to know if the transition has happened. [15:35] I understood Alt. was dead. [15:35] skaet, define "oversize"? [15:35] well, we probably didnt switch off the builds yet, not sure [15:35] skaet, I think it was agree to have a 750mb (or 780mb) iso this cycle [15:35] seb128: i think, which ones do we have a quick reaction on to bring below size. [15:35] so that would be the desktop one stretched to that size [15:35] seb128, bigger than 700mb - ie. we'll go to USB from CD [15:35] ie, powerpc being oversized is not importiant [15:36] Personally I'd like to see full disk encryption support in Ubiquity before the alternates go away. [15:36] cjwatson: ^ [15:36] skaet, I will have to check with pitti (or cjwatson maybe knows) but I think dropping DVD is alright [15:36] ScottK: note, netboot is unaffected. [15:37] ScottK: This is a requirement from Foundations' point of view; xnox is working on it. [15:37] cjwatson: I've been following the blueprint. [15:38] I can't say I care about oversizedness at all for alpha 1. We generally haven't much before. [15:38] Agreed. [15:38] cjwatson, agreed - mostly trying to figure out if DVD and alternates make sense to try for. [15:38] and currently we are still building alt. [15:39] Daviey: server/squashfs> I'd rather do a straight switch, not build both, personally. [15:39] and when we should be turning off alternates. [15:39] skaet: Not until foundations-q-ubiquity-lvm-luks is implemented, IMO. [15:39] cjwatson: do you mind, having both for A1? [15:39] cjwatson: I'd like easy direct comparison of the advantages. [15:39] Daviey: Yes, I do mind. It's a fair bit of complexity to bring up an extra image type temporarily. [15:39] ok\ [15:39] You can compare with the last daily before the switch, or with 12.04. [15:39] its a bit stressful wrt testing and build times too [15:40] cjwatson, ok, I'll use that blueprint as the trigger for turning off the alternate dailies. [15:40] ogra_: build times is 20 mins, and testing is via jenkins.. But i do see cjwatson's point. [15:40] Daviey, QA minds if that means testing both for A1 [15:40] I'm not sure who is going to do the KDE U/I bits for foundations-q-ubiquity-lvm-luks. [15:40] jibel: no, not releasing both... having both. [15:40] skaet: I'll add a work item to that spec for foundations to do that once we're satisfied [15:41] It's possible we'll still need alternates for Kubuntu due to lack of U/I to use the new feature. [15:41] thanks cjwatson. :) [15:41] ScottK: It's probably not *very* much work ... [15:41] jibel: but also looking to drop i386 as a released image.. so that makes your life easer :) [15:41] Daviey, Thanks so much :) [15:42] cjwatson: Maybe someone who's familiar with the code base because they just did a python3 port could look into it? [15:42] (since it's easy) [15:42] :-) [15:43] ScottK: Seeing as I've deferred this blueprint since 7.04, I think it's a good idea for Dmitrij to be having a go at this rather than me this time :-) [15:43] OK. [15:43] #action skaet to mail out summary of what we're trying for A1 early next week to ubuntu-release mail list, and what should be in final manifest, and make sure all teams are on the same page at next meeting. [15:43] ACTION: skaet to mail out summary of what we're trying for A1 early next week to ubuntu-release mail list, and what should be in final manifest, and make sure all teams are on the same page at next meeting. [15:43] :) [15:43] \o/ [15:44] The one person we have who's still around and has done Ubiquity work at all has almost no time this cycle due to work commitments. [15:44] yeah some sorting to do, definitely. .... [15:44] ..? [15:45] o/ [15:45] * skaet assumes we've thrashed that topic for now [15:45] ScottK go [15:45] For 12.04.1 preps: I mentioned in the Kubuntu status input we need three 4.8.3 packages accepted for precise-proposed. [15:45] Is there someone from ubuntu-sru that could look into that? [15:46] ScottK, Spamaps and RAOF are on point right now, ask question in #ubuntu-release [15:47] OK. [15:47] .. [15:47] :) [15:47] thanks. [15:47] We should probably get SRU representation at this meeting in the run up to 12.04.1 [15:47] .. [15:47] Daviey, yes, I think there may be a separate meeting about to form specific for 12.04.1, based on the blueprints. ;) [15:47] stgraber, ^ comments? [15:48] if no separate meeting, we'll continue to bring issues up here. [15:48] and cross polinate [15:48] (thanks ScottK :) ) === nhandler_ is now known as nhandler [15:48] yeah, still need to get the final list of attendees and figure out a time for it, but we'll have a separate meeting for 12.04.1 [15:48] likely fortnightly, at least until we get close to 12.04.1 [15:48] .. [15:49] thanks stgraber.. [15:49] once the meetings kick off, we can figure out logistics if it makes sense to have some else here, or if we can cover from folks who need to be in both already. [15:50] .. [15:51] I think most attendees will be in both anyway... :) [15:51] .. [15:51] ara, brendand - any updates on how the 12.04.1 certification is looking? [15:52] skaet: hi! [15:52] :) [15:52] thanks roadmr, was just looking to see if you were in the channel. :) [15:52] hmm, i was told certification strictly happens post release.. has that changed? [15:52] oops [15:53] meant to ask about 12.04 [15:53] lol [15:53] skaet: yes, was about to ask for clarification [15:53] * skaet needs to watch her fingers autoprogramming... [15:53] skaet, ara said in her mail report there would be nobody from the team in the meeting today [15:53] skaet: we still have some pending systems, expect them to be finished next week [15:53] any big worries showing up from the work so far? [15:53] skaet: some of our resources got repurposed so we've made little progress but should be back to full speed next week [15:54] skaet: nothing major, cert-blocking bugs are being reported... [15:54] skaet: and hopefully a few can be fixed in 12.04.1, that should unblock a few systems (for instance, some that won't install with the 12.04 kernel, we couldn't cert those :( ) [15:55] .. [15:55] roadmr, thanks for that. :) [15:55] roadmr: I assume there will be pre-cert on 12.04.1 images? [15:55] (pre-release) [15:56] (this didn't happen with 10.04.4) [15:56] please get the bug numbers associated with the systems that won't install mailed out to the ubuntu-release mail list as soon as possible, so we can make sure they're being planned for with the 12.04.1 release. :) [15:56] Daviey: hmm all I have is a full certification run once 12.04.1 is released, if you think pre-certing would be useful we can talk about that and see if we can manage [15:56] +1 [15:56] roadmr: okay, thanks :) [15:57] skaet: OK, we can email the ones we already have ASAP and send out another batch once we finish the remaining cert systems [15:57] roadmr, great. Thanks! :D [15:57] .. [15:57] .. from me as well [15:57] I think we're getting close to time for the meeting to wrap up. any one else have last questions? [15:58] lets go home. [15:58] Thanks everyone. :) [15:58] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [15:58] Meeting ended Fri May 25 15:58:36 2012 UTC. [15:58] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-25-15.01.moin.txt [15:58] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-25-15.01.html [15:58] thanks skaet ! [15:58] thanks [15:58] thanks skaet! [15:58] thanks :) [15:58] thanks! [15:58] thanks for chair'ing skaet [15:59] thanks skaet [16:00] thanks === allison is now known as wendar === wendar is now known as allison === allison is now known as wendar [21:06] ok [21:09] #startmeeting [21:09] Meeting started Fri May 25 21:09:16 2012 UTC. The chair is wendar. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [21:09] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [21:09] * stgraber waves [21:10] * ajmitch looks up the agenda for today [21:10] hi stgraber [21:10] #topic Action review === meetingology changed the topic of #ubuntu-meeting to: Action review [21:10] we covered the bugs pretty well at UDS, and came up with some new ones [21:11] Yeah, seems like a lot were closed at UDS. [21:11] we can drop any closed ones [21:11] in fact, we can probably replace that with a general review of the arb tag [21:11] some of those closed will change how much info we need to put into the packages as well, if I understood it correctly [21:13] asomething has found a few more that are quickly related, we could tag those & check up on them as well [21:13] * highvoltage jumps into the channel pool and causes a huge splash [21:13] hi highvoltage :) [21:13] ajmitch, they should be tagged arb already [21:13] hi! sorry for being late [21:13] asomething: excellent, thanks [21:14] ajmitch: yes, we're able to drop all the custom tags from debian/control, and no longer need the special image install in debian/rules [21:15] So, LP #914667 is now Fix Released, so dropping it from the agenda [21:15] Launchpad bug 914667 in Developer registration portal "Packages in the ARB process should go directly to Published without going to "Ready to Publish"" [High,Fix released] https://launchpad.net/bugs/914667 [21:16] now that we can see all app states, #915902 is also fixed & can be dropped [21:17] the state changing is apparantly going onto production on monday, according to a related bug [21:17] and #915902 is marked as Fixed Released, so dropped from the ARB tag, good... [21:17] https://bugs.launchpad.net/developer-portal/+bug/1004487/comments/1 [21:17] Launchpad bug 1004487 in Developer registration portal "Every piece of feedback should send an email to the ARB list" [Low,Confirmed] [21:19] #927588 is tagged with arb, so we don't need to manually track it [21:19] wendar: are you editing the wiki page at the moment? [21:19] nice to see that the bug list for the arb tag has come down so much [21:19] ajmitch: not at the moment, go ahead [21:20] #927588 is not tagged with arb yet, so I'll change that [21:20] * ajmitch was just going to track down a few blueprints & add them under work items [21:21] (it's a duplicate anyway, but good to keep it tagged so it gets cleaned up) [21:21] python-distutils-extra got a few fixes that landed in quantal that fix up some little arb/quickly things [21:22] asomething: great, thanks [21:22] 3 blueprints linked [21:23] asomething: yeah, it looks like that one is Fix Released, so we can drop it from the Agenda [21:23] no more lintian warnings about the copyright, no more unused cdbs build dep, no more deprecated {XS, XB}-python fields [21:23] asomething: ah, very nice, thank you [21:24] uds-q-community-q-upstream-outreach-latest [21:24] uds-q-desktop-q-quickly-latest [21:24] I assume we need to get the blueprints approved for quantal & with a milestone set for them to show on status.ubuntu.com [21:24] wendar: you want those added to the agenda? [21:25] ajmitch: yup, we've got ARB workitems on them too [21:25] uds-q-community-q-upstream-myapps-latest [21:26] ajmitch: give me the URLs of the ones you need release targeted and accepted and I'll do it [21:26] stgraber: some have already been done, but need to check which [21:26] ("done" meaning release targeted) [21:27] wendar: linked those 3 [21:28] stgraber: https://blueprints.launchpad.net/ubuntu/+spec/community-q-app-review-board is the only one unapproved, probably because I need to fill in the whiteboard from the pad [21:28] ajmitch: awesome, thanks! [21:29] ajmitch: done [21:29] stgraber: thanks [21:31] wendar: how's the pkgme backend coming along? [21:31] ajmitch: mostly done, I need to submit it to james for review [21:31] ajmitch: (as a branch or a patch, I'm not sure which) [21:32] branch, probably [21:32] does it call the other backends once it knows some of the information? [21:33] ajmitch: at the moment, no, it's completely standalone [21:33] ajmitch: we don't really need any information from the other backends [21:34] no, but it's useful to have the cmake backend run for cmake-using tarballs [21:34] ajmitch: specifically, the Python backend isn't allowed to run on the servers, because it executes arbitrary code [21:34] ajmitch: so for python code we can't use the Python backend at all [21:35] that's a shame, since python code is one of the easier ones to automate [21:35] ajmitch: what does the cmake backend add that's useful? [21:35] ajmitch: well, Python code is so easy to automate, we don't need the Python backend [21:35] ajmitch: our own is good enough [21:36] alright [21:36] ajmitch: I'll make a note to take a look at the cmake backend and see if it's work delegating or copying bits from it [21:36] *worth [21:38] * ajmitch thinks that there's probably some useful parts in the other backends [21:38] ajmitch: I'll take a look [21:38] ok [21:39] what other action items do we want to look at? [21:39] ajmitch: mainly, just make sure that all our action items from the pads are now in the blueprints [21:39] so they get tracked in status.ubuntu.com [21:39] looked like they should be there now [21:41] also check the priorities, lots are Undefined [21:41] as for the state of the queue, I've got a busy weekend ahead on submissions I've said I'd look at [21:43] ajmitch: great. [21:43] anyone know what team you need to be on to have your workitems show up on status.ubuntu.com? [21:43] asomething: afaik you don't need to be on any particular team, but have the blueprints in the right state [21:43] I'm guessing that https://blueprints.launchpad.net/ubuntu/+spec/community-q-app-review-board will appear in status.ubuntu.com after the next regeneration, since it's now Approved [21:44] asomething: you need to be added to the right team [21:44] wendar: oh you do? [21:44] https://launchpad.net/~ubuntu-community-contributors [21:44] * ajmitch came out of UDS with a relatively short list of work items [21:45] ajmitch: smart move :) [21:45] wendar: it can't be just that team, there's only 11 people in it :) [21:46] ajmitch: afaik, ubuntu developers also get added [21:46] I didn't seem to get ARB ones, but that means that when I have ARB time I can at least use it for looking at submissions. [21:46] ajmitch: but not all members [21:46] highvoltage: heh [21:46] flavours also get automatically added iirc [21:47] well, i'm already pending to join that team. guess I just need to bug someone to approve me. I am in ~ubuntu-dev though... [21:47] basically, if you're on one of these teams, you're good: http://status.ubuntu.com/ubuntu-quantal/teams.html [21:48] maybe we should get ubuntu-arb added to that... [21:48] wendar: that'd be good, bug against summit? [21:48] skaet: ^ [21:48] looks like ~ubuntu-dev needs to be there as well [21:48] asomething: why? [21:49] sorry (didn't realize this was the meeting channel) [21:49] micahg: it's ok, you can interrupt :) [21:49] micahg, I'd rather not have to join even more teams just to see my work item status. [21:49] * micahg would think something like MOTU might be worthy, but not sure about ubuntu-dev in general as a team [21:49] ajmitch: I'm also behind on the queue, I'm afraid I pretty much dropped off the map for two weeks after UDS [21:50] (moving and new job apologies) [21:50] wendar: so have I, apart from looking at some apps locally on my laptop I haven't really touched it [21:50] no need to apologise, it's a busy time for you :) [21:50] I'll also be trying to catch up this week [21:51] Last month some people did a Tuesday queue run [21:51] i did a few reviews, but nothing I looked at was in shape to suggest ya'll vote on it yet [21:51] did that seem useful? [21:51] I think it was useful [21:51] asomething: thanks! [21:51] would you like to do one next week? [21:51] * highvoltage also had to work last weekend so will actually take some time to relax this one [21:51] finding a time that highvoltage & I could work on the queue together was a challenge, but I think it's good to talk to someone else [21:52] ajmitch: should we try again next week the same time we've done it before? [21:52] what time did you finally end up with last time around? [21:52] it was 6am on a tuesday morning for me... that's... 10:00 UTC [21:52] 6AM for highvoltage, 10pm for me :) [21:52] asomething: if the ARB had a lot of WI, maybe that team should be on the status tracker as well (apologies if this was already proposed) [21:53] that was the only hour in the whole week we could align, we scanned through our entire schedule :) [21:53] *schedules [21:53] micahg: yep, that's the idea, that's why I also poked skaet [21:54] ok [21:54] * ajmitch personally wants to try & get a couple of apps through to voting each week if possible [21:54] ajmitch: yes, that sounds like a good goal [21:55] not too high, but we could keep up with the queue fairly quickly if we each did that [21:56]