[07:45] <pitti> jibel: bonjour
[07:45] <pitti> jibel, cjwatson: FYI, I burned current lucid daily on a CD and did a test install, went fine
[07:46] <jibel> pitti, Guten Morgen
[07:46] <jibel> cjwatson, pitti here are the results of the smoke test for 10.04.3
[07:46] <jibel> alternate|desktop i386|amd64 english|non-english : OK
[07:47] <jibel> alternate OEM: OK
[07:47] <jibel> desktop OEM: KO
[07:47] <jibel> I'll replay the desktop OEM in debug mode and will file a bug. The system always reboots to the stage 'Prepare for shipping'.
[09:05] <cjwatson> jibel: ok, thanks.  per skaet, we'll need to bump d-i to the new kernel too
[09:06]  * cjwatson goes to sort that out
[09:58] <cjwatson> jibel: did you get as far as filing that bug about the desktop OEM case?
[10:01] <jibel> cjwatson, I can't find a way to reproduce. I'll blame the tester.
[10:02] <jibel> so we can consider desktop oem is good too
[10:19] <cjwatson> jibel: OK, can the tester reproduce it? ;-)
[13:24] <jibel> hm, small but important detail ubuntu-server prompt says 10.04.2 LTS
[13:32] <cjwatson> oops
[13:33] <cjwatson> I thought I'd SRUed base-files for that
[13:33] <cjwatson> ... apparently not
[13:36] <cjwatson> pitti: ^- could you process my base-files upload to lucid-proposed?
[13:36] <cjwatson> damn, we'll need wubi too, I've been slack on dedaling with the checklist
[13:41] <cjwatson> ev: I can haz new ~ubuntu-installer/wubi/lucid build?
[13:41] <cjwatson> (r191)
[13:47] <pitti> cjwatson: oh, of course! the neat place card on the point release :)
[13:48] <pitti> cjwatson: btw, do we have a lucid-proposed freeze, or lucid-updates freeze?
[13:48] <pitti> we have two other unapproved lucid-proposed uploads in the queue
[13:48] <pitti> (neither seem urgent for .3)
[13:54] <cjwatson> given that it's six days away, I think we need to freeze -proposed for anything non-critical, but we should continue to validate and push to -updates
[13:54] <cjwatson> at some point in the next few days we'll need to assess anything that's not yet in -updates
[13:55] <pitti> cjwatson: ack
[13:57] <pitti> cjwatson: I suppose we want apt and python-apt, but it's just 2 days old; I guess we should just test it intensely, and release it on Monday?
[13:57] <pitti> I'm a bit hesitant to release system critical packages on a Friday, especially with much less than 7 days of age
[14:01] <cjwatson> pitti: apt and python-apt are there for Launchpad deployment work; I don't care whether they're in 10.04.3 are not
[14:01] <cjwatson> *or not
[14:01] <pitti> ah, ok
[14:28] <ev> cjwatson: will do after lunch
[14:29] <cjwatson> [6~[6~ta
[14:29] <cjwatson> er, "ta"
[14:39] <skaet> cjwatson, checklist calls for CRON job to be turned off today.   With the last minute churn, does it still make sense to do so?
[14:39] <cjwatson> I think tomorrow would make more sense
[14:40] <cjwatson> (my family's off to Oxford for the weekend; I'll be around)
[14:40] <skaet> okie.  thanks.
[14:44] <skaet> cjwatson,  will you create the candidate images when you turn off the CRON?
[14:45] <skaet> jibel,  can you  switch the iso tracker over to be testing 10.04.3 now,  so that when the images emerge we have a place to put them.
[14:45] <skaet> ?
[14:49] <cjwatson> skaet: yes
[14:49] <cjwatson> (I don't think cron is an acronym, BTW ...)
[14:50] <cjwatson> or rather, I will probably just publish the last round of daily builds as candidates
[14:53] <jibel> skaet, yes, I'll do shortly
[14:55] <jibel> google returns "Command Run ON" as acronym of CRON
[14:56] <cjwatson> I'd be surprised.  I think that's a retcon
[14:56] <cjwatson> unless somebody has a reference to bwk or dmr or somebody saying that :)
[14:56] <jibel> but the site stating that returns "Error 500" :)
[14:58] <cjwatson> http://unix.derkeiler.com/Newsgroups/comp.unix.bsd.freebsd.misc/2007-03/msg00328.html says it's a contraction of chronology or some similar time-like expression, which seems a lot more likely to me, but I can't find anything actually authoritative
[14:58] <skaet> :)
[14:58]  * skaet will stop captializing cron at any rate.... ;)
[15:44] <jibel> skaet, tracker for 10.04.3 is opened
[15:46] <skaet> Thanks jibel.  :)
[15:57] <micahg> skaet: hi, I'd like to make sure that thunderbird 3.1.11 gets on the 10.04.3 images if possible, it'll be going out today
[15:57] <micahg> oops
[15:58] <micahg> nevermind, it's not on the image
[15:58] <micahg> and xubuntu isn't releasing, so ignore me :)
[15:58] <skaet> micahg, its past freeze... not sures there's enough bake in time.
[15:58] <micahg> skaet: just realized it wasn't actually a problem
[15:59] <skaet> :)
[15:59]  * micahg has no idea what we're going to do WRT firefox and 10.04.4, but we can worry about that after UDS
[16:02] <micahg> oops, I meant to wait until the release meeting was over...
[16:05] <pitti> micahg: is it on the DVDs? skaet, are we even releasing 10.04.3 DVDs?
[16:05] <pitti> I'm not sure any more, but it seems to me that we did point releases without DVDs in the past
[16:06]  * micahg checks germinate
[16:06] <micahg> it is probably on the DVD
[16:07] <micahg> pitti: you're right, it's on the DVD ::(
[16:07] <cjwatson> I was planning to do DVDs if possible
[16:07] <micahg> and there were DVDs for 10.04.2
[16:07] <micahg> http://cdimage.ubuntu.com/releases/10.04.2/release/
[16:07] <pitti> micahg: hm, I don't see a Task: ubuntu-live-dvd header?
[16:07] <pitti> ubuntu-dvd-live, even
[16:08] <micahg> http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.lucid/dvd.seed
[16:08] <micahg> pitti: I don't recall ever seeing that
[16:08] <pitti> e. g. apt-cache show anthy
[16:08] <cjwatson> dvd not dvd-live
[16:08] <cjwatson> no Task field for that
[16:08] <pitti> ah
[16:14] <micahg> skaet: so, first, apologies for ping you during the release meeting
[16:14] <micahg> skaet: second, see above
[16:16] <micahg> it's a security update, so it generally goes straight in
[16:16] <micahg> I guess it's not the biggest deal either way since it'll be out of date again in 4 weeks
[16:19] <skaet> micahg, no worries about the ping during release meeting,  I've been accidentally guilty of the same myself to pitti this week.  :/
[16:20] <skaet> micahg, I'd prefer to keep the churn down right now,  since we're pulling in a later kernel than I'd like and we're supposed to be putting up candidates about now.
[16:21] <skaet> cjwatson,  what's your thoughts?
[21:00] <cjwatson> skaet: similarly would prefer to keep churn to a minimum if possible ...
[21:06] <micahg> skaet: cjwatson: it's a security update and unfortunately, I'm late in releasing it, what should I do?
[21:07] <micahg> jdstrand: ^^
[21:08] <jdstrand> why don't we turn off copy-report
[21:08] <jdstrand> then we can push to -security without it getting to -updates
[21:09] <cjwatson> sure
[21:10]  * jdstrand goes to do that
[21:10] <cjwatson> done
[21:10] <cjwatson> too late :)
[21:10]  * jdstrand refrains
[21:10] <jdstrand> :)
[21:10]  * micahg thanks cjwatson and jdstrand 
[21:10] <micahg> so I'm good to release now?
[21:12] <micahg> jdstrand: ^^
[21:12] <jdstrand> micahg: yeah, go ahead
[21:12] <micahg> jdstrand: thanks