=== Ursinha` is now known as Ursinha
=== Ursinha is now known as Guest90314
=== smb` is now known as smb
=== Guest90314 is now known as Ursinha
[14:00]  * skaet waves
[14:00]  * stgraber waves
[14:01] <skaet> 12.04.1 time?
[14:01] <stgraber> yep
[14:01] <stgraber> #startmeeting Ubuntu 12.04.1 team meeting
[14:01] <meetingology> 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] <meetingology> 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
=== 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 | Ubuntu 12.04.1 team meeting Meeting | Current topic:
[14:02] <jamespage> o/
[14:02] <stgraber> seb128 told me he won't attend this week's meeting but should be able to make it to the next ones
[14:02]  * stgraber pulls the list of attendees and does some pinging
[14:03] <stgraber> stokachu, arges, smoser: around?
[14:03] <smoser> o/
[14:03] <stokachu> o/
[14:04] <NCommander> stgraber: thanks
[14:04] <stgraber> right, so welcome to the first 12.04.1 team meeting
[14:04] <stgraber> I "think" we now have the final team list with jamespage and smoser being the two last additions (from the server team)
[14:05] <stokachu> arges is sick today so he wont make it
[14:06] <stgraber> stokachu: ok, thanks
[14:06] <stgraber> 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]  * stgraber tries to get LP to give him some useful bug lists
[14:08] <stokachu> i do have one for the server team
[14:09] <stgraber> stokachu: go ahead, while I'm digging for good bug lists :)
[14:09] <stokachu> ok
[14:10] <stokachu> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/520386, (mir @https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/904014)
[14:10] <ubottu> 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] <ubottu> Launchpad bug 904014 in netcf (Ubuntu) "[MIR] netcf" [Undecided,In progress]
[14:10] <skaet> 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] <skaet> however,  there's alot that's come in that needs to be looked at.
[14:11] <skaet> I know of several critical that aren't on that list.
[14:12] <skaet> bug 944546, bug 751689, bug 949641
[14:12] <ubottu> Launchpad bug 944546 in libcommons-cli-java (Ubuntu Precise) "StringIndexOutOfBoundsException in HelpFormatter.findWrapPos" [Critical,Triaged] https://launchpad.net/bugs/944546
[14:12] <ubottu> 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] <ubottu> 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] <smoser> bug 1003842
[14:13] <ubottu> 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] <skaet> several other high ones that are new as well...
[14:14] <stgraber> apparently not all of these are targeted for 12.04.1
[14:14] <stgraber> or rather, none of these :)
[14:15] <jamespage> sounds like that would be a good first action - review these bugs and others and target for 12.04.1
[14:15] <stokachu> for mine I'd like server team to review to see if its feasible to target for 12.04.1
[14:15] <stgraber> 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] <stgraber> 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] <stokachu> definately, just wanted to make sure its on the radar
[14:16]  * skaet nods
[14:17] <skaet> in terms of reviewing bugs,  scope should probably be wider than those mentioned above.
[14:17] <stgraber> 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] <smoser> so, to be clear, above, those bugs should have a 12.04 task and be targetted to 12.04.1 ?
[14:18] <stgraber> yes
[14:18] <skaet> should be a precise task, rather than 12.04 task,  but yeah.   ;)
[14:19] <skaet> milestone should be 12.04.1
[14:19] <stokachu> question, where do i set the task?
[14:19] <skaet> target to series
[14:19] <stokachu> ah
[14:20] <skaet> should give you the option.  :)   please mark it to quantal too, if its known to affect that one as well.
[14:20] <stokachu> gotcha
[14:21]  * xnox was told not to target to quantal as the default task status tracks that.
[14:21] <stgraber> 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] <stgraber> 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]  * xnox nods and agrees
[14:22] <skaet> +1,  makes it easier for finding.
[14:23]  * skaet is willing to help out with the series and target/milestoneing if needed too.
[14:23] <stgraber> 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] <skaet> indeed.   Most of them should be getting bug numbers associated with them,   but its good to see imapct.
[14:24] <skaet> or rather the high impact ones should be ;)
[14:24] <stgraber> 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] <stokachu> curious why 2,3 off that list dont have bugs associated?
[14:24] <stgraber> 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] <stgraber> stokachu: probably means that nobody with a similar stacktrace reported it to Launchpad
[14:25] <stokachu> ok
[14:26] <stgraber> so these should definitely be the priority as it means they aren't currently showing up on LP at all
[14:26]  * skaet nods
[14:27] <skaet> 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] <skaet> 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] <skaet> Its been updated now with the latest info from UDS.
[14:28] <skaet> (and subsequent discussions ;) )
[14:29] <skaet> 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] <skaet> in the QA columns,  look for events starting "P-".
[14:31] <skaet> If anyone has any questions about it,  feel free to ping me.
[14:32]  * skaet done
[14:32] <stgraber> thanks skaet
[14:33] <stgraber> so I quickly drafted an agenda for our next meetings: http://paste.ubuntu.com/1016424/
[14:33] <stgraber> does that seem to cover what people want to discuss here, did I miss something?
[14:34] <jamespage> LGTM
[14:34] <smoser> i think that looks good, skaet
[14:34] <skaet> stgraber,  looks fine by me.
[14:34] <stokachu> looks good
[14:35] <stgraber> cool, updated the google calendar event to include the agenda then
[14:35] <stgraber> 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] <stokachu> i dont atm
[14:36] <ScottK> 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] <ScottK> It's sched for release June 5.
[14:37] <stgraber> ScottK: what's the expected release date for 4.8.4?
[14:37] <jamespage> 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] <ScottK> If we follow the timeline we managed for 4.8.3, it should make it fine.
[14:38] <stgraber> ScottK: looks like you should have way enough time to have it packaged and pushed through the SRU process then
[14:38] <ScottK> Yes.
[14:38] <xnox> 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] <smoser> jamespage, verified your question against zul.
[14:39] <xnox> (just the all/most filesystems stack)
[14:39] <stgraber> 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] <skaet> xnox,  are there auto tests,  or are you looking for manal.
[14:39] <skaet> manual even.
[14:39] <skaet> ?
[14:40] <xnox> skaet: both. QA  install/upgrade tests with updated packages. both auto and some manual.
[14:40] <skaet> xnox,  for install/upgrade testing,  synch with gema and jibel.
[14:40] <xnox> 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.
=== sagaci_ is now known as sagaci
[14:41] <skaet> for the manual testing,  let baloons know the details of what you're looking for.
[14:41] <stgraber> xnox: are these changes already in quantal?
[14:41] <skaet> there's a slot scheduled for some precise testing in July,  may make sense to aim for that?
[14:41] <xnox> 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] <xnox> skaet: yes. Ok i will discuss it with people.
[14:42] <xnox> stgraber: some, not all yet.
[14:42] <xnox> [ACTION] xnox to prepare a target list for fs stack for 12.04.1
[14:42] <meetingology> ACTION: xnox to prepare a target list for fs stack for 12.04.1
[14:43] <stgraber> xnox: ok. Make sure these bugs are targeted to precise/12.04.1 so they show up on the list
[14:43] <xnox> [ACTION] xnox to liase with ballons, gema and jibel w.r.t. testing
[14:43] <meetingology> ACTION: xnox to liase with ballons, gema and jibel w.r.t. testing
[14:43] <xnox> stgraber: ok.
[14:43] <xnox> ..
[14:44] <skaet> :)
[14:44] <skaet> stgraber, can we use the .. convention in this meeting?
[14:44] <stgraber> skaet: sure
[14:44] <stgraber> ..
[14:44] <skaet> :D
[14:45] <stgraber> btw, might be worth pointing out that we have daily builds of precise going on at http://cdimage.ubuntu.com/precise/ (and other <product>/precise directories)
[14:45]  * xnox yeah =)
[14:46] <stgraber> skaet: do you know if QA is doing daily testing of these?
[14:46] <skaet> stgraber,  I'll take the action to get an update published.
[14:46] <jamespage> stgraber, are there plans for a -server daily image as well?
[14:46] <skaet> which mail list should we be using between meetings?
[14:47] <stgraber> jamespage: http://cdimage.ubuntu.com/ubuntu-server/precise/
[14:47] <jamespage> stgraber, thanks - found it at the same time :-)
[14:47] <skaet> 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] <skaet> ..
[14:48]  * skaet suggests ubuntu-release
[14:48] <xnox> [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] <meetingology> 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] <stgraber> 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] <skaet> coolio.   and thanks xnox
[14:49] <stgraber> ..
[14:49] <stgraber> can everyone make sure they are subscribed to ubuntu-release@lists.ubuntu.com?
[14:50] <xnox> #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]  * xnox just old stuff
[14:50] <stgraber> 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] <skaet> sounds good.  :)
[14:51] <xnox> stgraber: well meetingology generates a good base template =)
[14:51] <xnox> if used properly
[14:51] <stgraber> so hopefully the next meeting will be better structured and properly announced, sorry for the last minute scheduling ;)
[14:51] <stgraber> anything else?
[14:52] <xnox> [TOPIC] AOB
[14:52]  * xnox I guess the chair should be doing the commands....
[14:52] <skaet> :)
=== tumbleweed_ is now known as tumbleweed
[14:52] <NCommander> 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] <stgraber> 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] <stgraber> 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)
=== sary_ is now known as sary
[14:54] <NCommander> will do so
[14:54] <stgraber> #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
[14:54] <meetingology> Meeting ended Thu May 31 14:54:30 2012 UTC.
[14:54] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-31-14.01.moin.txt
[14:54] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-31-14.01.html
[14:54] <stgraber> thanks everyone!
[14:54] <jamespage> ttfn
[14:55] <skaet> thanks stgraber for getting this kicked off.  :)
[14:56] <jibel> stgraber, can you add me to the list of attendees please, so I won't miss the next meeting  ?
[14:57] <stgraber> jibel: I knew I'd be forgetting someone ;) sorry for that, added.
[14:58] <xnox> stgraber: as I took some actions, can you please invite me for the next one as well please.
[14:58]  * xnox not sure if i want/need to attend it every time
[14:59] <jibel> np :)
[14:59] <stgraber> xnox: invited you to the next one
[14:59] <xnox> StevenR: cool thanks =)
=== dutchie_ is now known as dutchie
=== lamont` is now known as lamont
=== ogasawara_ is now known as ogasawara
=== ScottK2 is now known as ScottK
=== jalcine is now known as Jacky