14:01:42 #startmeeting Ubuntu 12.04.1 team meeting 14:01:42 Meeting started Thu May 31 14:01:42 2012 UTC. The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:01:42 14:01:42 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 14:02:05 o/ 14:02:25 seb128 told me he won't attend this week's meeting but should be able to make it to the next ones 14:02:51 * stgraber pulls the list of attendees and does some pinging 14:03:29 stokachu, arges, smoser: around? 14:03:29 o/ 14:03:37 o/ 14:04:01 stgraber: thanks 14:04:29 right, so welcome to the first 12.04.1 team meeting 14:04:59 I "think" we now have the final team list with jamespage and smoser being the two last additions (from the server team) 14:05:59 arges is sick today so he wont make it 14:06:11 stokachu: ok, thanks 14:06:53 the idea behind this meeting is that every 2 weeks until the release of 12.04.1, we can do a quick review of what still needs to land, what's broken and not fixed yet and make sure we have resources working on these 14:08:24 * stgraber tries to get LP to give him some useful bug lists 14:08:40 i do have one for the server team 14:09:39 stokachu: go ahead, while I'm digging for good bug lists :) 14:09:43 ok 14:10:04 https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/520386, (mir @https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/904014) 14:10:06 Launchpad bug 520386 in libvirt (Ubuntu Lucid) "libvirt-bin hypervisor does not support virConnectNumOfInterfaces / unable to create domain with virt-manager using network bridge" [Low,Confirmed] 14:10:07 Launchpad bug 904014 in netcf (Ubuntu) "[MIR] netcf" [Undecided,In progress] 14:10:09 stgraber, http://status.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html has what teams still have on their commit to fix list. 14:10:22 however, there's alot that's come in that needs to be looked at. 14:11:05 I know of several critical that aren't on that list. 14:12:32 bug 944546, bug 751689, bug 949641 14:12:36 Launchpad bug 944546 in libcommons-cli-java (Ubuntu Precise) "StringIndexOutOfBoundsException in HelpFormatter.findWrapPos" [Critical,Triaged] https://launchpad.net/bugs/944546 14:12:37 Launchpad bug 751689 in linux (Ubuntu Precise) "ThinkPads overheat due to slow fans when on 'auto'" [Critical,Triaged] https://launchpad.net/bugs/751689 14:12:39 Launchpad bug 949641 in fglrx-installer (Ubuntu Precise) "Installing both fglrx and fglrx-updates results in: error exit status 1 -"/etc/init.d/atieventsd exists during rc.d purge"" [Critical,Triaged] https://launchpad.net/bugs/949641 14:13:03 bug 1003842 14:13:05 Launchpad bug 1003842 in network-manager (Ubuntu) "dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers" [Medium,Confirmed] https://launchpad.net/bugs/1003842 14:13:22 several other high ones that are new as well... 14:14:26 apparently not all of these are targeted for 12.04.1 14:14:37 or rather, none of these :) 14:15:05 sounds like that would be a good first action - review these bugs and others and target for 12.04.1 14:15:21 for mine I'd like server team to review to see if its feasible to target for 12.04.1 14:15:49 yeah, it's always easy to decide later on that they won't make it for 12.04.1 and re-target to -updates or 12.04.2 14:16:13 ideally, https://launchpad.net/ubuntu/+milestone/ubuntu-12.04.1 should be an up to date representation of what's going on with 12.04.1 14:16:19 definately, just wanted to make sure its on the radar 14:16:24 * skaet nods 14:17:40 in terms of reviewing bugs, scope should probably be wider than those mentioned above. 14:17:46 so I think it'd make sense to always first target to 12.04.1 when we see a bug that we think should be fixed for 12.04.1, then let the team responsible for the package make the decision of doing it for 12.04.1 or postponing to 12.04.2/-updates (with a reason, ideally :)) 14:17:59 so, to be clear, above, those bugs should have a 12.04 task and be targetted to 12.04.1 ? 14:18:09 yes 14:18:51 should be a precise task, rather than 12.04 task, but yeah. ;) 14:19:05 milestone should be 12.04.1 14:19:39 question, where do i set the task? 14:19:52 target to series 14:19:55 ah 14:20:17 should give you the option. :) please mark it to quantal too, if its known to affect that one as well. 14:20:55 gotcha 14:21:12 * xnox was told not to target to quantal as the default task status tracks that. 14:21:22 if you don't have the right to target/milestone bugs, ping me and I'll do it for you, but I guess most of us have the required rights 14:22:04 xnox: it does but it's rather confusing, so I usually prefer to explicitly target to quantal (which makes the default task disappear) 14:22:19 * xnox nods and agrees 14:22:20 +1, makes it easier for finding. 14:23:15 * skaet is willing to help out with the series and target/milestoneing if needed too. 14:23:22 another source of bugs that we didn't mention yet but is really important for the point release is https://errors.ubuntu.com 14:23:53 indeed. Most of them should be getting bug numbers associated with them, but its good to see imapct. 14:24:07 or rather the high impact ones should be ;) 14:24:08 it'd be good to have someone from each engineering team go through that list once a week or so and make sure that any frequent crasher is properly milestoned to 12.04.1 and that someone from there team is actively working on a fix 14:24:48 curious why 2,3 off that list dont have bugs associated? 14:24:50 I can't remember exactly what we said in the UDS session, but looking at the current state, anything that crashes > 100 times a day, should probably be actively investigated at this time 14:25:42 stokachu: probably means that nobody with a similar stacktrace reported it to Launchpad 14:25:55 ok 14:26:18 so these should definitely be the priority as it means they aren't currently showing up on LP at all 14:26:40 * skaet nods 14:27:34 getting the teams looking at the errors.ubuntu.com list is a bit of a culture change, and this is a good place to start that behaviour changes from. ;) 14:28:14 Other info that might be useful is that the schedule for 12.04.1 can be found: https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule 14:28:26 Its been updated now with the latest info from UDS. 14:28:36 (and subsequent discussions ;) ) 14:29:31 If people want to know when we'll be having testing windows, prior to that release, the information for that is captured on: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock 14:29:53 in the QA columns, look for events starting "P-". 14:31:16 If anyone has any questions about it, feel free to ping me. 14:32:16 * skaet done 14:32:35 thanks skaet 14:33:29 so I quickly drafted an agenda for our next meetings: http://paste.ubuntu.com/1016424/ 14:33:45 does that seem to cover what people want to discuss here, did I miss something? 14:34:00 LGTM 14:34:07 i think that looks good, skaet 14:34:41 stgraber, looks fine by me. 14:34:43 looks good 14:35:06 cool, updated the google calendar event to include the agenda then 14:35:48 does anyone have something they wish to discuss at this meeting? any controversial bug or something that should be considered for 12.04.1? 14:36:02 i dont atm 14:36:34 Just as a mention ... KDE SC 4.8.3 hit precise-updates yesterday. We may (not sure) be able to get 4.8.4 in before 12.04.1. 14:37:01 It's sched for release June 5. 14:37:02 ScottK: what's the expected release date for 4.8.4? 14:37:47 smoser: I'm right in saying the first set of SRU updates for openstack should land in -proposed in the next week or so? 14:38:02 If we follow the timeline we managed for 4.8.3, it should make it fine. 14:38:10 ScottK: looks like you should have way enough time to have it packaged and pushed through the SRU process then 14:38:18 Yes. 14:38:35 well I have requests to update ef2progs, btrfs-tools, mdadm and lvm2 for 12.04.1. I have/will prepare -sru's but I need qa assistance to test those. 14:39:04 jamespage, verified your question against zul. 14:39:07 (just the all/most filesystems stack) 14:39:28 xnox: do you just need testers or very specific setup? my feeling so far is that the QA team doesn't have a whole lot of time to help with SRU verification 14:39:33 xnox, are there auto tests, or are you looking for manal. 14:39:40 manual even. 14:39:42 ? 14:40:14 skaet: both. QA install/upgrade tests with updated packages. both auto and some manual. 14:40:48 xnox, for install/upgrade testing, synch with gema and jibel. 14:40:55 My access to QA/kernel machines with multiple disks for RAID testing is still pending. And I don't want to push mdadm stuff to precise without testing it first. 14:41:05 for the manual testing, let baloons know the details of what you're looking for. 14:41:31 xnox: are these changes already in quantal? 14:41:35 there's a slot scheduled for some precise testing in July, may make sense to aim for that? 14:41:43 stgraber: not really SRU testing, more general overall testing - it may work as an sru, but fresh .1 install or upgrade from lucid may go haywire and I don't have capacity to test that. 14:42:04 skaet: yes. Ok i will discuss it with people. 14:42:12 stgraber: some, not all yet. 14:42:52 [ACTION] xnox to prepare a target list for fs stack for 12.04.1 14:42:52 * meetingology xnox to prepare a target list for fs stack for 12.04.1 14:43:16 xnox: ok. Make sure these bugs are targeted to precise/12.04.1 so they show up on the list 14:43:20 [ACTION] xnox to liase with ballons, gema and jibel w.r.t. testing 14:43:20 * meetingology xnox to liase with ballons, gema and jibel w.r.t. testing 14:43:29 stgraber: ok. 14:43:52 .. 14:44:01 :) 14:44:21 stgraber, can we use the .. convention in this meeting? 14:44:34 skaet: sure 14:44:37 .. 14:44:44 :D 14:45:13 btw, might be worth pointing out that we have daily builds of precise going on at http://cdimage.ubuntu.com/precise/ (and other /precise directories) 14:45:48 * xnox yeah =) 14:46:06 skaet: do you know if QA is doing daily testing of these? 14:46:46 stgraber, I'll take the action to get an update published. 14:46:50 stgraber, are there plans for a -server daily image as well? 14:46:57 which mail list should we be using between meetings? 14:47:05 jamespage: http://cdimage.ubuntu.com/ubuntu-server/precise/ 14:47:19 stgraber, thanks - found it at the same time :-) 14:47:51 by update published, meant to say, update on the status of whether these are all being run still in jenkins, and where to find the results. ;) think they are, but need to double check. 14:47:58 .. 14:48:13 * skaet suggests ubuntu-release 14:48:31 [ACTION] skaet to get an update on the status of daily QA testing of whether these are all being run still in jenkins, and where to find the results. 14:48:31 * meetingology skaet to get an update on the status of daily QA testing of whether these are all being run still in jenkins, and where to find the results. 14:48:32 skaet: good question, mostly depend on the expected trafic I guess. Any of -release, -qa or -devel would be appropriate but -release is probably the best as it's likely of interest of most subscribers 14:48:54 coolio. and thanks xnox 14:49:14 .. 14:49:34 can everyone make sure they are subscribed to ubuntu-release@lists.ubuntu.com? 14:50:22 #agreed to target all relevant bugs to the milestone, such that https://launchpad.net/ubuntu/+milestone/ubuntu-12.04.1 shows a useful summary. 14:50:37 * xnox just old stuff 14:50:48 I'll be posting the meeting notes for this meeting, create a wiki page and put the agenda of the next meeting there and announce all that to ubuntu-devel and ubuntu-release 14:51:08 sounds good. :) 14:51:15 stgraber: well meetingology generates a good base template =) 14:51:22 if used properly 14:51:32 so hopefully the next meeting will be better structured and properly announced, sorry for the last minute scheduling ;) 14:51:59 anything else? 14:52:18 [TOPIC] AOB 14:52:32 * xnox I guess the chair should be doing the commands.... 14:52:37 :) 14:52:47 We have highbank enablement stuff coming down the piple, but details are a bit light on when specifically, will get back to when they are all in 14:53:02 xnox: yeah, I only wrote the agenda half way through the meeting, so using [TOPIC] now doesn't make a lot of sense :) but will definitely use the bot for the next one 14:53:58 NCommander: ok, make sure any related bugs is targeted to precise/12.04.1 and that any other required changes (images?) is announced to -release (or at the next meeting) 14:54:24 will do so 14:54:30 #endmeeting