[00:01] slangasek: should I be pre-publishing images now? [00:06] Riddell: if you have good images, then yes :) [00:13] slangasek: so I do for-project .. publish-release .. poolonly to pre publish? then what do I do tomorrow to publish them? [00:23] charlie-tca: ok to publish xubuntu images? [00:23] stgraber: ok to publish edubuntu images? [00:24] Riddell: yep [00:25] * robbiew probably should work on a release announcement, huh? [00:26] robbiew: https://wiki.kubuntu.org/MaverickMeerkat/RCAnnouncement would be a start [00:26] yeah...I think skaet started it already [00:27] I started that [00:27] oh...Riddell did [00:27] :) [00:27] where's rick to sign off on ubuntu images? [00:27] will need to update https://wiki.ubuntu.com/MaverickMeerkat/TechnicalOverview as well [00:28] yes indeed [00:29] jiboumans: ok to publish ubuntu server images? [00:31] Riddell: I don't believe they need to sign off on the images [00:31] they = rick and jos [00:32] if the ISOs cleared the isoqa process, then they are good to go [00:34] I'm going by https://wiki.kubuntu.org/MaverickMeerkat/ReleaseManifest, there's a few failures on ISO tracker so I wouldn't say that counts as cleared [00:35] e.g. http://iso.qa.ubuntu.com/qatracker/test/4564 has two failures on live session and one on wubi [00:40] aye [00:41] Riddell: well you might not get a response from either today :/ [00:42] Riddell: tomorrow you run publish-release again with 'yes' instead of 'poolonly' [00:43] slangasek: for each of the classes of image? [00:43] for all images that belong on releases.u.c [00:43] yep [00:44] and you'll want to make sure you stow the beta images away in ../old-images/ before you start publishing with 'yes', otherwise bits go awol [00:46] slangasek: is that just done by hand? [00:46] sadly, yes [00:52] 30/09 00:51:16 shes gonna het off with some fitty then [00:52] >> (30/09 00:51:18) (Laney[+Ris]) (39:sarah_pearce16) [00:52] >> (1=1 |#crumbs 2=2 |#php 3=3 |#short.bus 4=4 |#haskell 5=5 |#toast~ers 6=6 |#debian-uk 7=7 |#relax 8=8 |#deb~n-cli 9=9 |#agda [00:52] >> (0=10|#ubu~lease q=11|#ubu~-motu w=12|#ubu~devel e=13|#ubuntu-uk r=14|#epigram t=15|&bitlbee y=16|#ubunt~ing u=17|#debian i=18|#debi~evel [00:52] argh [00:52] multitouch + x clipboard = bad combination [00:55] Laney: it's an entertaining combination though [00:56] I accidently paste things so often, it's pretty shameful really [00:57] slangasek: for publishing on cdimages I use "named" in the command? [00:57] Riddell: correct [00:57] slangasek: what happens if I use "no"? [00:58] Riddell: then you get images published with naming in the style of alphas (i.e., without the release version in the filename) [00:59] ok, not what I want then [01:00] slangasek: what do I have to do to publish wubi (if anything)? [01:02] Riddell: that's not part of the RC checklist, is it? I don't know that we "release" wubi until the end [01:02] Riddell: but the process is to grab the URL returned by 'find-live-filesystem i386 wubi' and wget that into the release dir [01:03] (and call it 'wubi.exe', or something else sensible) [01:03] I'd have thought RC was ment to follow the final release as closely as possible, isn't it ment to be a practice run? [01:05] that's not how I understand it [01:05] there's lots of other stuff happening on release day that we don't go through for the RC - the RC is really just a last test of the archive+images before the point of no return [01:06] It's also an extra good excuse to make developers get their heads out of random code and remember that a release is happening, and they have to fix that niggling bug *NOW* [01:19] Riddell, were you asking about ubuntu studio publication? [01:19] i think we should be good :) [01:19] ScottL: I was [01:20] Riddell, is there anything specifically you needed? [01:20] https://wiki.kubuntu.org/MaverickMeerkat/ReleaseManifest says I need LuisdeBethencourt to sign off, but if you can prove you're also responsible for it that's good [01:21] Riddell, i do not think you will get his sign off ;) i am current project lead however, you can validate that with persia and themuso if necessary [01:22] * persia hunts up the email to ubuntu-release [01:22] Oh, u-d-a actually: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-September/000766.html [01:22] persia: do you trust this guy? or is he just a one bit shift plageriser of ScottK? :) [01:22] ScottL, You should probably update the wiki [01:23] Riddell, I trust ScottL [01:23] persia, i shall update the wiki later tonight (kids are acting up) [01:23] Actually someone other than ScottL should update the wiki. [01:23] (and yes, nick-completion gets useless at that level of similarity) [01:23] ScottK, Who ought it be? [01:23] I can update the wiki [01:23] Excellent. [01:23] Oustanding [01:23] Great! [01:23] err. Outstanding ;) [01:23] persia: I don't think people should be self-appointed to the release manifest. [01:24] ScottK, We probably ought formalise that then, as we've historically mostly self-appointed release manifest entries when we added them. [01:25] I agree with your point, but it needs documentation, review by appropriate teams (ubuntu-release? TB?), announcement, etc. [01:25] persia: I don't know that it has to be a formal rule, just a best practice. [01:25] That's easier to implement :) [01:26] persia: The release delegations are different than ISO signoff in any case. [01:26] (re your earlier comment) [01:27] Ah, that's my failure in not being familiar enough with the release approval process then. [01:28] (both in referencing that, and in not ensuring that ScottL was listed there previously) [01:28] We'll survive. [01:30] slangasek: the .pool directories look good, I presume I use sync-mirrors to push them out? [01:31] Riddell: yep [01:32] syncing [01:54] * Riddell snoozes === bjf is now known as bjf[afk] [06:10] Riddell, around? [06:42] skaet, he claimed to be snoozing about 270 minutes ago: he's probably still doing so :) [06:43] heh, spotted that, but he wasn't marked away, so figured I'd check. :) [06:44] * skaet figures its time for her to go sleep too, it can wait until the morning. [06:44] Won't hurt to leave a contentful ping, and check your backscroll in the morning... :) [06:45] (plus someone else might have the data you seek) [06:58] Thanks persia, I sent a long email a while ago now, mostly its just trying to sort out who'll do what tomorrow between him, Robbie and myself ;) The TechnicalOverview needs some love on its release notes for the known issues. [07:00] GIven your timezone, I suspect you'll end up with whatever isn't already done when you get up :) [07:00] lol, yup. [08:14] good morning all! [08:34] charlie-tca: ping, xubuntu sign off needed [08:35] jiboumans: ping, server sign off needed [08:36] weird weechat doesn't save anymore channels on close… [08:41] well it's only wee, next time try mucklechat :) [09:25] could someone please reject my foomatic-gui upload? it appears that needs a bit of clarification with till first [09:27] mvo, done [09:36] thanks seb128 [09:45] ogasawara: please check kernel info on https://wiki.kubuntu.org/MaverickMeerkat/TechnicalOverview [09:52] Riddell, pointing to the kubuntu wiki, uh? :) [09:53] Riddell, in known bugs thare are some from last milestone [09:53] ara: I think didrocks is making some edits, please coordinate with him to get them updated [09:54] will release the lock shortly [09:54] Riddell, shouldn't be skaet doing that? or the one acting as RM [09:54] who is in charge? [09:55] yes skaet said she could do it too [09:56] done for me === doko_ is now known as doko [11:36] please accept lash, if possible [11:36] It's in the Studio set. [11:37] ahh, ok [11:43] doko, Generally https://launchpad.net/ubuntu/maverick/+queue?queue_state=1&queue_text= will show if stuff is in a set (use queue_text if the list is too long) [11:55] Riddell: mountall 2.19 is serious for cloud, nice-to-have for everything else [11:56] good, thanks [11:56] Riddell: do you know about publish-image-set.py in lp:ubuntu-archive-tools? [11:57] Riddell: it doesn't run them for you, but it saves having to come up with all the publish-release commands by hand [11:57] cjwatson: I did not [11:58] pitti wrote it for alpha-3 or so, and I polished it a bit for beta; it's not quite there yet but it's a heck of a lot easier than byhand [11:58] hah, bet it doesn't know about "RC" mind you ... [11:58] * cjwatson goes to fix it [11:59] doesn't look like it [12:01] fixed [12:02] is this a bad sign "Making armel+omap zsync metafile ... too long between blocks (try a smaller block size with -b)" [12:10] ok images all in place except those omap ones which zsync breaks on [12:10] cjwatson: any idea what that's about? [12:11] now we just need sign off from server, the ubuntu website people to do whatever the ubuntu website people need to do, publish, announce [12:13] beasties still need updated on https://wiki.kubuntu.org/MaverickMeerkat/TechnicalOverview [12:13] ogasawara needs to update linux version numbers too [12:13] uh, I vaguely remember having to do some weird stupid thing with zsync [12:14] curiously the kubuntu omap images published fine [12:14] let me poke about a bit before I answer [12:15] but ubuntu-netbook and kubuntu-mobile broke [12:15] which exact command? [12:15] (s) [12:18] actually never mind, I'll just see if I can make it cope in general [12:19] ARCHES='armel+omap armel+omap4' for-project ubuntu-netbook publish-release ports/daily-preinstalled 20100929 preinstalled-netbook named rc #FAILED [12:21] try it again now [12:22] * Riddell tries [12:23] "too long between blocks (try a smaller block size with -b) Trying again with block size 2048 ..." clever :) [12:23] still a zsyncmake bug, but there you go [12:27] slangasek: I'd appreciate it if you would have a look at the kdebase-workspace upload in queue (it's a one line change to it's upstart script). The rationale sounds reasonable and the code does what the rationale says, but i have no idea if it's the right idea. [12:37] Riddell, publish of ec2/uec images is done from nectarine.canonical.com [12:37] cjwatson also has acl [12:37] documented at https://wiki.ubuntu.com/UEC/Images/Publishing [12:40] hmm [12:43] well I don't seem to have access to nectarine [12:43] cjwatson: can you publish the UEC images? [12:44] yeah [12:45] what build id? [12:46] 20100928.4? [12:48] are we ready to push go ? [12:48] if so i can do it [12:48] or we can let cjwatson [12:49] also for uec images i have to update AMI pages on amazon, which i can/will do [12:49] I probably ought to learn how to do it [12:49] yeah. [12:49] ok. [12:50] well, i'm kind of here. if you fall over. [12:51] i've already pre-published that image. i dont think you've ever been shared aws login info to do "Updating Amazon Pages" [12:51] so I run 'sudo -u vmbuilder /home/vmbuilder/bin/cronrun promote-daily rc /srv/ec2-images/server/maverick/20100928.4', yes? [12:51] I'm probably best off not trying to do the amazon update [12:52] oh, I add --make-public? [12:52] so 'sudo -u vmbuilder /home/vmbuilder/bin/cronrun promote-daily --make-public rc /srv/ec2-images/server/maverick/20100928.4'? === rgreening_ is now known as rgreening [12:53] (awaiting ack before pressing enter) [12:55] verifying [12:56] vbcron promote-daily release /srv/ec2-images/server/maverick/20100928.4/ --verbose --make-public [12:56] oh. and vbcron is just sudo -u vmbuilder (in ~vmbuilder/bin) [12:56] so yeah. [12:56] hit enter [12:58] you had 'release' not 'rc'? [12:58] oh carp [12:59] i did. [12:59] we need to run with 'rc' [12:59] does it require any kind of cleanup of the previous publication? [13:00] i'll handle that. its all public [13:00] err... private [13:00] Looks like Omg Ubuntu! has already announced the RC [13:00] should I let you do this at this point? :) [13:01] yes. i'm sorry. i can't believe i did that. [13:01] nhandler: someone has to jump the gun :) [13:01] Slashdot always announces the release several hours early. [13:02] ok. cjwatson i just started: vbcron promote-daily --make-public rc /srv/ec2-images/server/maverick/20100928.4 --allow-existing --verbose [13:02] * cjwatson nods and logs out :) [13:03] it will take like 3 hours :-( [13:03] at least the last one did. [13:05] and worse, its largely network bandwidth bottlenecked [13:05] smoser: who's bandwidth? [13:06] whose [13:06] outbound from canonical [13:06] well canonical -> aws [13:07] obviously its not saturated, but i don tthink that a release grab is going to help it. [13:09] smoser: if this is nectarine, you're on a link that's essentially unaffected by RC or anything else [13:09] oh. it is nectarine. [13:09] Riddell: I'm ok with RC [13:09] * cjwatson leaves a comment on behalf of the release team on the omgubuntu page [13:10] ttx: thank, I'll publish those then [13:10] I don't imagine slashdot will ever change their spots but at least omgubuntu could do better [13:10] I'm having problems with that conference connection [13:11] smoser/Daviey: you can confirm for me [13:11] I don't see it on slashdot [13:11] ttx, ? [13:12] smoser: that RC is "ready to ship" for you [13:13] ttx: confirm? [13:13] well, no. [13:13] it was ok. [13:13] but we're a couple hours away now. [13:14] as i fat-fingered the pre-publish yesterday [13:14] smoser: for the normal server images, not cloud [13:15] smoser/Daviey: Riddell has been asking me if I could signoff for RC [13:15] smoser/Davieyyou know ths situation better than I do [13:15] and that flaky connection can go down any time [13:15] ttx: Yes.. it's looking good. [13:16] ttx: Nothing major has arisen with the pre-rc tests [13:16] in mdz style I am slightly spooked by the lack of need for last-minute respins [13:17] cjwatson: that's because you rock :) [13:17] smoser/Daviey: great [13:19] wow, those omgubuntu people are cheeky [13:19] ok. i have to get away from the machine for a bit. the publish will be done when it is done. [13:19] "perhaps you should work _with_ us" it's not like we're hard to find if they want to ask [13:20] and it will update: http://uec-images.ubuntu.com/query/released.latest.txt [13:20] Riddell: After they published a screed about how awful Ubuntu devs were, I decided I wasn't interested in them anymore. [13:21] Maverick is looking better that i expected :) [13:21] didrocks: gnome version numbers still don't match https://wiki.kubuntu.org/MaverickMeerkat/RCAnnouncement [13:21] so anyone interested can just : while sleep 10m ; do wget http://uec-images.ubuntu.com/query/released.latest.txt | grep "maverick.*rc" && mpg321 NarwhalsNarwhals.mp3; done [13:21] Low expectations will do that for you. [13:24] Riddell: sorry, should have forget to save the edit, fixed. [13:25] so now we need skaet or someone to update the bugs on https://wiki.kubuntu.org/MaverickMeerkat/TechnicalOverview, ogasawara to fill in her version for the linux bit, newz to copy it over to the ubuntu website [13:27] Riddell: if you don't need me anymore, I'll disappear again [13:27] ttx: thanks, you can go [13:28] Riddell: thank you for a smooth milestone release ! [13:28] and they're all on the wrong side of the planet so I guess we have to wait [13:34] or I could just assume the announcement is ok, ignore the ubuntu website and announce [13:34] that's what I would do if I was an omgubuntu editor :) [13:35] :) [13:35] where is the known issues page template ? [13:36] * ogra wants to check that all notes made it from the bugs to that page [13:37] Riddell, ? ^^^ [13:39] ogra: bottom of https://wiki.kubuntu.org/MaverickMeerkat/TechnicalOverview [13:39] thanks [13:39] * ogra cross checks [13:40] can i edit there ? [13:40] its all blue ! [13:42] You can. We allow it. [13:42] heh [13:42] ;-) [13:44] Riddell: Can I start reviewing/accepting seeded packages from the queue? [13:44] (normally once we're into publishing that's OK) [13:44] hrm [13:45] * ogra would edit if he could log in ... seems to be some heavy load on the wiki atm [13:49] ScottK: aye go for it [13:49] OK. Thanks. I'll work doko's NBS stuff. [13:50] Benjamin Humphrey got in touch with me by /msg as requested, but when I replied eight minutes later he'd already /quit ... [13:50] * cjwatson sighs [13:54] Sigh. [13:54] lamont: Why are all the i386 buildd's on manual? [13:55] Is there an estimated time they'll be back? [14:03] You'd think that news sites could, you know, check the website. [14:03] skaet, hello, are you around? [14:04] wgrant: That's not a recipe for being first. You have to have proper priorities. [14:09] ara: skaet seems to still be asleep [14:09] I've announced on kubuntu.org but the ubuntu e-mail announce will probably need to wait for her [14:10] Riddell, but there are some bugs on the release notes that are already fixed [14:10] ara: yes that's what I'm waiting to be updated [14:11] Riddell, i.e. bug 628681 [14:11] Launchpad bug 628681 in ubiquity (Ubuntu Maverick) (and 1 other project) "Kubuntu OEM did not install oem-config-kde (dup-of: 628290)" [High,Triaged] https://launchpad.net/bugs/628681 [14:11] Launchpad bug 628290 in ubiquity (Ubuntu Maverick) (and 1 other project) "OEM installation, missing "Prepare for shipping to end user" icon (affects: 2) (dups: 2) (heat: 167)" [High,Fix released] https://launchpad.net/bugs/628290 [14:11] Riddell, OK, no worries, I'll talk to her when she's around :) [14:17] Riddell: We're going to have trouble moving these post-RC builds through with no i386 builders. Perhaps you could have a poke at IS and find out what's up and when we can expect to have them back? [14:18] ScottK, i'm happy to share the arm ones (though we would have to delay the release i guess ;) ) [14:18] I can chase it [14:19] Heh. Probably. [14:19] ScottK: that was Ng [14:19] cjwatson: Thanks. [14:19] he's doing the bootstrap [14:19] that you guys asked for - he should only be a couple more minutes he says [14:19] OK. [14:19] cjwatson: ^^^ mystery resolved. [14:19] ah, normally bootstraps don't require taking all the buildds down for more than a few moments [14:20] the procedure I remember is "stop buildds, get nominated buildd to accept package you want, re-enable them all"? [14:20] cjwatson: essentially, yes [14:20] cjwatson: yep. and wait for it to fetch and at least start unpacking the buildd [14:20] s/buildd$/tarball/ [14:20] OOo is needed, but will take a while :-/ [14:21] (fix uninstallables on armel) [14:21] cjwatson: sorry yeah it's taking me a bit longer than it should [14:24] ok they're back on auto now, sorry about that [14:24] thanks! [14:27] Ng: Is the build in question tiles? [14:28] yeah [14:28] It bounced onto vernadsky a minute or two ago. [14:28] Was that intentional? [14:28] no, it seems to be unhappy [14:29] Threaten to build it -j 16 on armel if it doesn't behave. [14:29] ScottK: you joke, but foomatic already does that :-/ [14:30] elmo: Yeah, I knew I wasn't making that up. [14:30] lamont says that makes the buildd very angry. [14:39] I'd appreciate it if someone would review/accept clamav. Once that's in Maverick, I'm ready to upload it to lucid-updates ... [14:51] "The following link will direct you to a download location near you" ... "Or, choose the mirror closest to you" why do we need the second if we have the first? [14:51] ScottK: let me look [14:52] Riddell: Thanks. === doko__ is now known as doko [14:56] ScottK: done [14:56] oh, sorry, Riddell was in progress on it apparently, didn't notice [14:56] Thanks both of you. [14:57] too late by only seconds, no glory for me [15:03] Riddell: heh [15:03] as if the accepter is visible anywhere anyway ... [15:11] ah, good morning skaet [15:11] good morning Riddell :0 [15:12] :) [15:12] hey skaet [15:12] skaet: release is mostly done, just needs you to update the beasties on https://wiki.kubuntu.org/MaverickMeerkat/TechnicalOverview [15:14] Riddell, cool. Need some of robbiew's input on some of the entries too. [15:14] oh, tsk, when does he wake up? [15:14] He's two hours east of skaet, so I guess whenever he feels like it. [15:15] Riddell, ScottK - actually robbiew and I are both in Austin. ;) [15:15] Oh. [15:15] That's right, I had you confused with the Oregon mob. [15:16] Sorry [15:16] ScottK, no worries ;) [15:17] Riddell, haven't seen answers from newz2000 yet either in the inbox, about the paths [15:17] * elmo posts to OMGUbuntu that the 'release is [...] done', you heard it here first [15:17] skaet: he's on irc though [15:17] what do you NEED from me? [15:17] just a review of the TechnicalOverview [15:17] ? [15:17] skaet, I am pretty sure that bug 628290 is fixed in RC, and should be removed from the notes [15:17] Launchpad bug 628290 in ubiquity (Ubuntu Maverick) (and 1 other project) "OEM installation, missing "Prepare for shipping to end user" icon (affects: 2) (dups: 2) (heat: 167)" [High,Fix released] https://launchpad.net/bugs/628290 [15:18] text for the bugs and known issues. [15:18] many of the "Known issues" there are from Beta [15:18] robbiew, text for the bugs and known issues. [15:18] ara, if its good, then yes it should be removed. [15:19] skaet, yes, but if that one is there, I think most should be checked :) [15:19] I just took the beta and then double checked the status on launchpad. [15:19] ara, :yup agree. that's what I put in the note to robbiew ;) [15:20] what needs tso be added today are the ones from the release target, and the one's we've found since beta and deferred. [15:20] sorry...I can't do it right now...ara can you verify? [15:20] robbiew, I'll have a look [15:20] thnx [15:26] Riddell, newz200 is responding to us, can you doublecheck the paths on the announce part and update with any input from him. Asked him about a couple of the fixme paths at the same time, so we should hear from that. [15:26] ? [15:26] skaet, I commented out two bugs that are fixed in RC. You can double check now === bjf[afk] is now known as bjf [15:27] ara, thanks! :) will do. [15:27] I am going to review now the bugs found during RC testing, to see what's worth adding to the release notes [15:28] seb128, didrocks, did you guys added this one to the release notes? https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/561734 [15:28] Launchpad bug 561734 in mesa (Ubuntu) (and 2 other projects) "quadrapassel doesn't start: Failed to initialise clutter: Unable to select the newly created GLX context (affects: 27) (dups: 7) (heat: 153)" [High,Fix committed] [15:29] ara: I didn't [15:29] ara, no, is one game really worth rc notes? [15:29] ara: but yeah, impacted intel driver, can have been added to the release note [15:29] and it's in the queue now, right? [15:29] yes [15:29] seb128, it is the only clutter application? [15:29] yes [15:30] OK, so if you think it is not worth it, that's fine [15:30] I would not bother for one game especially when the fix is in the queue [15:30] OK [15:30] but if somebody want to add it I'm fine with it [15:31] ara, but thanks for pointing it ;-) [15:31] I would be interested to get feedback on whether the fix work for you when it gets in [15:32] Riddell: why is sun-java6 in NEW? [15:33] seb128, sure, let me know when it reaches the archive, and I will check the fix [15:34] ara, I will, thanks [15:34] can someone please reject the desktopcouch upload in the queue? i just found a serious bug, there will be a new release asap [15:34] doko: because Brian uploaded it? [15:35] kenvandine, seems it got accepted already [15:35] Riddell: no, I did [15:35] ok... so that puts more pressure on a new release :) [15:35] kenvandine, it was over an hour ago, how broken is it? [15:36] it will likely break all quickly apps [15:36] will make didrocks happy [15:36] hehe [15:36] better fix it soon then :) [15:36] CardinalFang is busting it out now :) [15:36] oh nice :) [15:36] didrocks, see you though they could do anything else after breaking oneconf, they did :p [15:36] * didrocks loves more and more desktopcouh, breaking quickly apps and oneconf :) [15:36] seb128: hehe, right [15:37] I think I either hate it or it hates me :) [15:37] didrocks, the wrapper object created from get_records no longer contains a rows method [15:37] or any other for that matter [15:38] * CardinalFang is pale enough. Wearing this brown paper bag will not help. [15:38] hum, yeah, that's anoying [15:38] annoying* [15:38] CardinalFang: heh, don't be! [15:39] I'm astonished this slipped through tests. [15:42] doko: well that'll be why it's there then, packages which have been deleted then uploaded will go through New [15:43] Riddell: why deleted? it's in lucid partner [15:43] doko: https://edge.launchpad.net/ubuntu/+source/sun-java6/+publishinghistory says "Deleted on 2010-04-30 by Colin Watson [15:43] remove partner packages copied over when initialising maverick; these should only be in lucid for now" [15:52] doko: the partner team instructed us to do this [15:52] cjwatson: ahh, ok [15:52] they want to start partner afresh for every release [15:53] brian didn't know about it [15:53] he asked for it [15:53] (we won't have to delete them manually in future; Soyuz has been changed to avoid copying them) [15:53] skaet, from the bug list at iso.qa.ubuntu.com I don't see any supercritical worth mentioning (apart from those on the list) [15:54] ara, thanks for checking. :) [15:55] saw the bugs you commented out, we need to doublecheck launchpad is up to date on those, since they were not in "fixed released" state last night, which is why I left them in. [15:56] * robbiew is off the phone now...sorry :/ [15:56] skaet, both were bugs that were marked as duplicated of others [15:57] skaet, the original ones are "Triaged" and "Won't Fix" (the ones in the release notes) but if you follow the links, the master bugs are Fixed released [15:57] in versions contained in the cd [15:57] ara, thanks. it was a bit late. ;) [15:58] :) [15:59] ok. cjwatson Riddell uec images are now public [16:01] cjwatson, Riddell: what is the difference between "release notes" and "technical overview?" [16:02] I've never worked that out [16:02] that makes me feel so good [16:02] * newz2000 isn't the only one [16:02] Riddell: I'm unconfirming the URLs I confirmed [16:02] I thought the technical overview WAS the release notes [16:02] ok [16:03] for release notes they will be http://www.ubuntu.com/getubuntu/releasenotes/1010 the technical overview will live on the wiki [16:03] (wherever it is now) [16:04]