Started logging meeting in #ubuntu-meeting
[10:00:50] <skaet> Happy New Year all!
[10:00:50] <skaet> Not sure if we'll have quorum or not, but a quick run through of the agenda, so we know the questions to ask this week seems appropriate.
[10:00:52] <marjo> happy new year to all!
[10:01:25] <skaet> Agenda can be found: https://wiki.ubuntu.com/ReleaseTeam/Meeting/StableReleaseAgenda
[10:01:25] <skaet> Reminder, please follow the convention of using ".." on a separate line when you've finished typing. Also, If someone wants to comment on the last point, please "o/", so we know to wait.
[10:02:10] <skaet> and with that probably a good idea to start off...
[10:03:02] <skaet> [TOPIC] open action items
[10:03:52] <skaet> marjo - any update on the SRU test reports being added into the agenda?
[10:04:16] <marjo> skaet: please mark that one done; we'll include starting this week
[10:04:33] <skaet> awesome! thanks marjo.
[10:04:55] <skaet> victorp, how about the cert ones?
[10:05:41] <skaet> hmm, no victorp yet...
[10:05:51] <skaet> any other updates to the open action items?
[10:06:13] <skaet> ok, moving on
[10:06:28] <skaet> [TOPIC] Bug updates
[10:07:03] <skaet> since last month there's been about +37 bugs opened for maverick, +24 on lucid.
[10:07:24] <pitti> urgh; hopefully most of them as part of SRU uploads?
[10:07:43] <skaet> not sure
[10:08:03] <skaet> just started looking at the numbers this morning, and I think some serious triaging may be needed.
[10:08:29] <skaet> esp. with 10.04.2 scheduled for next month the lucid ones are a bit of a concern.
[10:08:33] <marjo> skaet: will follow up w/ bdmurray re: triaging
[10:08:42] <skaet> thanks marjo. :)
[10:09:20] <skaet> pitti, where are things standing with karmic SRU release right now? (did one go out?)
[10:09:42] <victorp> skaet - hi
[10:09:56] <pitti> skaet: very few; basically the kernel churn, and there are two untested papyon/tomboy packages in -proposed
[10:09:59] <pitti> ..
[10:10:17] <skaet> thanks pitti.
[10:10:36] <sconklin> What about the Karmic kernel still in -proposed?
[10:11:22] <pitti> sconklin: untested, and -ec2 doesn't even have a tracking bug
[10:11:34] <pitti> see bug 683474
[10:11:36] <ubottu> Launchpad bug 683474 in linux (Ubuntu Karmic) "Karmic: 2.6.31-22.70 -proposed tracker" [Undecided,Incomplete] https://launchpad.net/bugs/683474
[10:11:53] <sconklin> we're only testing maverick and lucid
[10:12:05] <sconklin> Karmic falls back to the old "time in proposed"
[10:12:44] <skaet> hmm, this probably needs to be made clearer then in the process docs.
[10:12:53] <skaet> if that's the concensus.
[10:13:13] <pitti> so we still need someone in the community to install and test that kernel
[10:13:40] <marjo> pitti, sconklin: pedro tested http://people.canonical.com/~pedro/kernel/kernel-2.6.31-22.70/
[10:13:59] <sconklin> well, Ideally everything would get all testing, but we're resource-bound
[10:14:20] <skaet> we schedule runs (of earlier) in when there are gaps with maverick/lucid testing?
[10:14:25] <bjf> marjo, that's the right kernel
[10:14:28] <pitti> marjo: ah, nice! so we can consider this done
[10:15:01] <pitti> sconklin: so that leaves the -ec2 one
[10:15:04] <pitti> bug updated
[10:15:15] <marjo> pitti: only if we agree that HW cert tests did not have to be run, see bug report please
[10:15:29] <pitti> marjo: it was a security update only, so I think that's fine
[10:15:38] <marjo> pitti: ack
[10:15:40] <sconklin> marjo, victorp, skaet - I'm dependent on the people who do the testing to determine what's possible. We need to figure out what we're doing as a rule and document it
[10:15:41] <pitti> we just need to guard against misbuilds and grave errors here
[10:15:48] <smb`> pitti, sconklin I guess i can try to get some generic boot/regression testing done for ec2 either today or tomorrow
[10:15:54] <sconklin> pitti: agreed
[10:16:04] <sconklin> smb`: thanks
[10:16:04] <pitti> smb`: that sounds fine
[10:16:07] <skaet> sconklin, pitti, agreed.
[10:16:15] <pitti> ec2 is basically just on kvm, isn't it? so that shouldn't be too hard to test
[10:16:19] <victorp> sconklin - agreed , I am happy to document the hwcert part , let me know where
[10:16:29] <skaet> smb thanks.
[10:17:00] <skaet> ok, moving on...
[10:17:07] <skaet> [TOPIC] 10.04.2
[10:17:36] <skaet> sconklin, any update on the kernel milestoned bugs?
[10:18:08] <sconklin> There was one bug milestoned, and I just chatted with Robbie - it's probably going to be rescheduled
[10:18:53] <skaet> thanks sconklin. :)
[10:19:13] <skaet> any one around from foundations today? (cjwatson's on holiday)
[10:19:46] <skaet> hmm, no bugs tagged against server at the moment so we're good there.
[10:19:59] <skaet> pitti, any update on the desktop milestoned ones?
[10:20:07] <pitti> skaet: I updated the wiki page
[10:20:18] <skaet> pitti, thanks! :)
[10:20:19] <pitti> the summary is that none of them are currently being worked on
[10:20:36] <pitti> one is just a "do it" thing (geode), the other two are pretty much "won'tfix"
[10:20:59] <pitti> we don't currently have active work on 10.04.2 in teh desktop team
[10:21:04] <pitti> is there something we should focus on?
[10:21:06] <pitti> ..
[10:21:34] <skaet> any chance we'll get someone to work on OOo?
[10:21:48] <skaet> between now and Feb?
[10:21:51] <ogra> skaet, see the ML, doko already did it seems
[10:22:14] <pitti> skaet: question for Jason, I don't have an update since december
[10:22:17] <pitti> holidays..
[10:22:30] <pitti> doko heroically packaged LibO for natty, though
[10:22:38] <pitti> (not finished yet)
[10:22:39] <skaet> ogra, cool. will look into it a bit more. was just looking at top level status this morning.
[10:23:10] <skaet> pitti, fair 'nuf. will follow up with jason, and keep fingers crossed on the rest.
[10:24:14] <skaet> will dig into the 10.04.2 bugs in more detail this week and next. release is 2/17, so there's still time.
[10:24:26] <skaet> any questions/comments?
[10:24:47] <micahg> about 10.04.2 in general?
[10:24:53] <skaet> [TOPIC] Stable Release Updates
[10:25:03] <skaet> micahg, yup sorry...
[10:25:22] <micahg> yes, I was wondering about the release timeline WRT freezes
[10:25:47] * micahg apologizes for not raising a hand
[10:26:30] <skaet> micahg, no worries. will take an action to set the date, and broadcast.
[10:26:53] * skaet will go back into the precedent emails :)
[10:27:15] <skaet> anyone else?
[10:27:42] <skaet> ok, back to Stable Release
[10:28:01] <skaet> sconklin, know you're just back, but anything on the hot plate?
[10:28:20] <sconklin> Not that I'm aware of, but I haven't even cleared email yet
[10:28:26] <ogra> same here
[10:28:34] <doko> skaet: what di you to know about foundations?
[10:28:43] <skaet> thanks sconklin, ogra
[10:29:09] <skaet> doko, just wondering if any updates on the 10.04.2 milestoned bugs from foundations team.
[10:29:49] <doko> sorry, don't know
[10:30:01] <skaet> no worries.
[10:30:37] <skaet> pitti, sconklin - so I'm guessing no need for a hw cert run, or regression runs this week?
[10:30:53] <pitti> skaet: not that I can see
[10:31:11] <rtg__> if there are resources, then how about testing karmic?
[10:31:13] <sconklin> skaet: we're going to discuss today whether we can upload a new cycle start by Friday.
[10:31:26] <skaet> victorp, marjo ^^
[10:31:33] <marjo> skaet: ack
[10:31:48] <skaet> sconklin, ack
[10:32:11] <bjf> rtg__, discussed and someone is on it
[10:32:16] <skaet> rtg__, see earlier in log.
[10:32:54] <skaet> sconklin, victorp, marjo, when is the next reasonable date to aim for lucid/maverick then?
[10:32:56] <victorp> rtg_ we would like to focus this week on natty
[10:33:03] <rtg__> sorry, my machine wedged and I must have missed it
[10:33:29] <victorp> skaet - date to start or to release?
[10:33:34] <sconklin> skaet: we'd really like to hit Friday upload but don't know if we can make it
[10:33:48] <bjf> victorp, what's natty? :-)
[10:33:52] <victorp> skaet - I would like to avoid a "2nd week" during the rally
[10:34:05] <sconklin> We'll let everyone know by tomorrow morning
[10:34:08] <skaet> victorp, sconklin - how about aim for testing cycle, week after rally then, and release that thursday?
[10:34:08] <victorp> bjf - dont know anymore :)
[10:34:17] <sconklin> That would put first week during the rally
[10:34:41] <sconklin> "Verification Phase"
[10:34:45] <marjo> skaet: two possible conflicts: 1) rally 2) US holiday 17 January
[10:35:03] <skaet> marjo, sconklin - true
[10:35:06] <marjo> skaet: more concerned about rally conflict
[10:35:20] <victorp> skaet - I wanted to clarify one thing - if we call it a "regression week" and we release on thursday, that means that the proposed kernels for regression have to be made available the thursday before, right?
[10:35:22] <marjo> but should be manageable
[10:36:06] <victorp> marjo - not for hw cert as laptops need to be rebooted manually and might not have anyone in the lab
[10:36:10] <skaet> victorp, yes, kernels should be avail week before.
[10:36:23] <victorp> skaet - thanks
[10:36:25] <marjo> victorp: ack
[10:36:46] <sconklin> let's please try to use the names "verification phase" and "testing phase"
[10:36:47] <skaet> so, should we just aim for releasing on Jan 20, or Jan 27?
[10:37:06] <skaet> sconklin, I'll go mark up the interlock that way if it will help.
[10:37:46] <sconklin> skaet: yeah, naming was not handled well by me at the outset, and I'm trying to unify everything now
[10:37:50] <sconklin> thanks
[10:38:01] <skaet> ok - will do.
[10:38:06] <victorp> sconklin ack
[10:38:56] <victorp> skaet - I vote for the 27th
[10:39:01] <skaet> right now shedule has 1/6 and 1/27 as release dates for SRU targets. Does it make sense to drop 1/27 and just go with 1/20?
[10:39:03] <skaet> heh
[10:39:24] * skaet types too slow for victorp
[10:40:00] <skaet> if there's nothing on the hot burner, some focus on natty and the lucid 10.04.2 bugs makes sense.
[10:40:07] <victorp> skaet - 1/20 means the verification phase is during the rally, is that ok?
[10:40:30] <skaet> victorp, good point.
[10:40:35] <marjo> skaet: if we're voting, then i vote for release on 1/27
[10:40:39] <skaet> ok, 1/27 it is.
[10:41:21] <skaet> any other topics to discuss today on the SRU side?
[10:41:49] <skaet> going once?
[10:42:01] <skaet> twice?
[10:42:08] <skaet> ok, probably time to end the meeting.
[10:42:16] <ogra> \o/
[10:42:16] <skaet> thanks everyone for participating. :)
[10:42:21] <skaet> #endmeeting
Meeting ended.