[00:00] <cjwatson> Saviq: I dealt with unity8
[00:00] <Saviq> cjwatson, awesome, thanks
[00:44] <knome> infinity, hey! :)
[00:45] <infinity> stgraber: So, how do I mark a milestone released in the tracker, so I can turn dailies on again and not overwrite all the entries?
[00:45] <knome> infinity, we need to upload a new xubuntu wallpaper relatively soon... would you approve a UIFe bug if we filed it quickly, even if we didn't have all the things prepared quite yet (naturally described though)
[00:46] <infinity> knome: If you're just swapping around images, a new wallpaper isn't a feature, IMO.  Just a UIF thing, and since you handle all your own docs, the only people you're hurting is yourselves if you have to take new screenshots.
[00:46] <infinity> knome: (Unless you're drastically changing the structure of the package or something?)
[00:47] <knome> infinity, that's why i said UIFe, and no, we're not doing weird changes. just to get it socially accepted
[00:47] <infinity> knome: Oh, you really did say UIFe.  I've had a long day.
[00:47] <knome> no problem :)
[00:47] <infinity> knome: If you want me to tell you your wallpaper's pretty, I can do that. :)
[00:47] <knome> of course!
[00:48] <knome> ;)
[00:48] <infinity> knome: But yeah, from a docs perspective, I imagine the only person whose approval you need is your own.
[00:48] <knome> yeah. we're fine docs-wise, we're not shipping screenshots
[00:48] <infinity> knome: And I think I trust you enough not to ship a wallpaper that's a 20x20 grid of naked breasts.
[00:48] <knome> hmm...
[00:48] <infinity> Okay, I *did* trust you.
[00:48] <knome> that opens a whole new possibilities
[00:48] <knome> hah :)
[00:49] <knome> i'll get the butt... i mean bug filed
[00:49]  * knome whistles
[00:49] <ScottK> infinity: Nudity is traditional for Ubuntu anyway.
[00:50]  * knome makes a mental note to start working on the wallpaper earlier next cycle
[00:50] <knome> fourth time in a row when we go over the UIF deadline...
[00:51] <infinity> knome: Also, no screenshots?  Do you not have a ubiquity slideshow, or do you just cop out and use the Ubuntu one?
[00:51] <knome> we have ubiquity slideshow, but our screenshots do not have the wallpaper pictured :)
[00:51] <infinity> Ahh.  Handy.
[00:51] <knome> and the slideshow background itself is just an arbitrary blue background ;)
[00:52] <knome> nobody will ever notice the difference anyway...
[01:13] <knome> infinity, bug 1298711
[01:13] <ubot2> Launchpad bug 1298711 in xubuntu-artwork (Ubuntu) "[UIFe] New Xubuntu wallpaper" [Undecided,New] https://launchpad.net/bugs/1298711
[01:13] <knome> infinity, and since i want you to say the wallpaper is pretty: http://temp.knome.fi/.w/xubuntu-trusty.png ;)
[01:14] <knome> the changes are in the branch as well.
[01:14] <infinity> knome: Too much yellow, rejected.
[01:14] <knome> oh shoo ;)
[01:15]  * infinity checks the branch for sanity.
[01:15] <knome> yeppers.
[01:16] <infinity> knome: Looks good.
[01:16] <knome> as you happened to say "yellow", i have to show you this another variant we considered... http://temp.knome.fi/.w/trusty-yellow.png
[01:20] <infinity> apw: I'm guessing that's not the "final upload", since there are apparmor things on the table and such still, right?
[01:44]  * infinity isn't even remotely in the mood to review that libreoffice upload...
[02:56] <stgraber> infinity: admin => milestones => edit => mark as released
[02:56] <stgraber> done that for you now
[02:57] <infinity> stgraber: Oh, I keep forgetting there's an admin thing.
[02:57] <infinity> stgraber: Thanks.  I shall go re-cron the world shortly.
[02:59] <infinity> stgraber: Can we ditch /home/ogra/sync-phablet-images entirely?
[02:59] <infinity> (world re-cronned)
[03:01] <stgraber> infinity: I have no idea what that script does, but hopefully it can die, yes :)
[03:01] <infinity> stgraber: I'll poke Oli about it sometime.  It's been commented out for ages, so I assume it's dead code.
[03:02] <infinity> stgraber: Figured you might know, since you're more involved in the phone image stuff.
[03:03] <stgraber> I maintain system-image, as far as s-i is concerned, you could give it ubuntu core images or tarballs of lolcats, it really doesn't care ;)
[03:04]  * infinity feeds system-image tarballs of locales for the next week.
[07:42] <Mirv> note qtlocation FFe bug #1298208 lacking from the changelog
[07:43] <ubot2> Launchpad bug 1298208 in qtlocation-opensource-src (Ubuntu) "[FFe] Qt Location sync packaging with Debian (new binary package)" [Wishlist,Triaged] https://launchpad.net/bugs/1298208
[09:41] <seb128> can somebody approve the libffi revert in unapproved?
[09:41] <seb128> update-manager, apport (and probably others) segfault on start with the libffi update from this night
[09:42] <seb128> that's going to bite beta upgrader if they can't run update-manager again
[09:42] <seb128> to get the fixed version
[09:42] <infinity> Lemme diff it against 3.0.13-12 and accept it.
[09:43] <seb128> doko_, btw, how come that new libffi was uploaded with a ffe?
[09:43] <seb128> it seems weird that upload was accepted in the first place :/
[09:43] <seb128> infinity, thanks
[09:43] <infinity> Yes, I'm still curious WHO accepted it.
[09:43] <infinity> And hoping the answer isn't "doko".
[09:44] <infinity> Though, a syncpackage as an AA might skip the queue, I can never remember.
[09:44] <Laney> 27/03 17:26:17 -queuebot:#ubuntu-release- Unapproved: libffi (trusty-proposed/main) [3.0.13-12 => 3.1~rc1-2] (core) (sync)
[09:44] <Laney> 27/03 18:16:42 -queuebot:#ubuntu-release- Unapproved: accepted libffi [sync] (trusty-proposed) [3.1~rc1-2]
[09:45] <infinity> Okay, that definitely looks like a human was involved.
[09:45] <infinity> And I'd like to think no one on the release team thought "hey, a new RC version of a core system library, that sounds safe". :/
[09:49] <infinity> Now, here's hoping nothing was rebuilt against the new libffi that now needs to be re-rebuilt.
[09:49] <infinity> (Can someone more awake than I am try to sort that out?)
[09:51] <seb128> infinity, let me try to have a look
[10:05] <Laney> infinity: were you looking at apparmor?
[10:05]  * Laney la la la
[10:06] <didrocks> infinity: if it's binary only through sync, it skips the queue, no?
[10:06] <didrocks> that's what I see for daily-release/CI Train
[10:07] <didrocks> (hence the NEW review at the publication beforehand)
[10:08] <infinity> didrocks: Hrm?
[10:08] <infinity> didrocks: Yes, binary NEW skips the queue on copies.  Has nothing to do with the libffi thing, which was in unapproved, and manually accepted by $someone.
[10:08] <Laney> he's asking if copies with NEW binaries skip the NEW queue
[10:08] <Laney> for qtlocation
[10:09] <didrocks> Laney: no no, I was talking about libffi based on infinity's remark
[10:09] <Laney> oh I see!
[10:09] <didrocks> infinity: yeah, there is the UNAPPROVED queue anyway, so human…
[10:10] <infinity> \o/ for Qt5 syncing with Debian.
[10:10] <infinity> Well, bits of it.
[10:31] <Laney> Daviey: There's curtin and simplestreams in unapproved, you interested?
[10:32] <Laney> They might or might not relate to bug #1281760 and bug #1281767 which never got replied to
[10:32] <ubot2> Launchpad bug 1281760 in curtin (Ubuntu) "FFE: curtin enhancements for 14.04" [Undecided,New] https://launchpad.net/bugs/1281760
[10:32] <ubot2> Launchpad bug 1281767 in simplestreams (Ubuntu) "FFE: simplestreams by-hash storage" [Medium,New] https://launchpad.net/bugs/1281767
[10:34] <Laney> smoser: ^^^ are those still relevant?
[10:37] <cjwatson> infinity: syncpackage as an AA doesn't skip the queue - I was very careful to make that a separate flag, not purely which team you're in
[10:38] <infinity> cjwatson: Right, --auto-approve.
[10:38] <infinity> cjwatson: I was just hoping for an excuse for that libffi accept that didn't look like malice or incompetence. :P
[10:38] <infinity> cjwatson: But the 1h window between it hitting the queue and leaving again make it clear a human was involved, either the uploader, or a reviewer who really didn't review.
[10:46] <ogra_> infinity, /home/ogra/sync-phablet-images can completely go from crontab
[10:46]  * ogra_ was meaning to clean that up a while ago but never got to it
[10:48] <infinity> ogra_: Kay, thanks.
[11:05] <knome> infinity, hey, ##StartTrustyReleaseBugs and ##End... were used to include the common infra bugs to flavor release notes, added them back as you had removed them from the wiki page either accidentally or on purpose; on the latter case, what's the new desired way?
[11:06] <infinity> knome: I probably just removed them when doing copy and waste to make the new release notes.
[11:06] <knome> ok, that's good
[11:07] <infinity> knome: Though, honestly, I don't see the value in per-flavour release notes at all.  I thought we'd settled last release on a single shared page.  People keep rethinking this every two months. :P
[11:07] <knome> that's fine to me
[11:07] <knome> we should just do the change then
[11:08] <knome> i can make xubuntu appear in the main release notes, if that's the goal..
[11:08] <infinity> knome: I'll bring it up on the -release list when I'm not (still) awake at 5am, and we'll sort it one way or another before final and make sure everyone's doing the same thing.
[11:09] <knome> great.
[11:19] <didrocks> seb128: autopkgtest for glib2.0 2.40.0-1: FAIL (Jenkins: public, private)
[11:19] <didrocks> on libiffi
[11:19] <didrocks> in case you didn't look
[11:19] <Laney> fixed
[11:19] <Laney> well, it worked on a retry ...
[11:19] <Laney> racy tests ...
[11:20] <seb128> didrocks, thanks
[11:20] <didrocks> yw, was browsering proposed-migration for powerd :)
[12:05] <Daviey> Laney: Yeah, i'll take a look shortly
[12:13] <Daviey> How are we currently handling seeded packages that aren't Beta blocking?
[12:17] <Laney> Daviey: Beta's done, can you be more specific?
[12:20] <Daviey> Laney: Oh, I missed Final Beta.
[12:21] <Daviey> See the mail now. thanks
[12:21]  * Laney nods
[12:42] <smoser> Laney, by hash storage not. (1281767)
[12:43] <smoser> Laney, the upload in queue for curtin fixes 1281760 (all but LVM/raid).
[12:44] <Laney> smoser: ok, looks like Daviey accepted those
[12:44] <Laney> please mangle the bugs as appropriate
[12:51] <Laney> doh, missed arm64 in gtkpod
[14:04] <stgraber> could someone please look at bug 1297363?
[14:04] <ubot2> Launchpad bug 1297363 in systemd (Ubuntu) "[FFe] Add cgmanager support" [Undecided,New] https://launchpad.net/bugs/1297363
[14:31] <stgraber> if whoever ends up reviewing the LXC upload wants an upstream changelog to check against, we have https://linuxcontainers.org/news
[14:31] <stgraber> I'll also be applying for an MRE for LXC 1.0.x in 14.04 as it's way easier for us to fix bugs upstream then do a point release than maintain and document dozens of cherry-pick (as we've been doing until 1.0)
[14:32] <zul> can someone accept cinder as well (LP: #1299010) please
[14:32] <ubot2> Launchpad bug 1299010 in cinder (Ubuntu) "FFE for cinder 2014.1.rc1" [Undecided,New] https://launchpad.net/bugs/1299010
[14:33] <stgraber> zul: I'm going through the queue now (for those which aren't my own uploads that is)
[14:33] <zul> stgraber: thanks
[14:34] <Laney> Pasting a git shortlog into a bug as its only content isn't the most useful FFe ever
[14:35] <stgraber> it's also not terribly good practice to upload to the queue before the FFe has been reviewed by the release team...
[14:36] <doko> what is the oif package set?
[14:36] <stgraber> rejected from the queue for now and commented in the bug with a comment similar to Laney's
[14:37] <seb128> doko, open input framework (the Ubuntu/Unity touch stack), why?
[14:38] <doko> seb128, http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140307-trusty.html ftbfs everywhere
[14:40] <zul> stgraber:  hey we are starting to get openstack rc1 out the door today and on monday....if its ok i was going to create a single bug for all of the openstack components and get the release team to ack it
[14:42] <stgraber> zul: single bug with per-package tasks should be fine, so long as you to a bit more work on describing what's new than you did with cinder
[14:42] <zul> stgraber:  sure
[14:42] <seb128> doko, well, I guess somebody is going to have to debug it, it didn't get any work for cycle and chase left Canonical a while ago
[14:49] <rbasak> How does the release team feel about me pushing an MRE for mysql-5.5 at this point in the cycle? Or should I just wait for release?
[14:50] <rbasak> It's on my todo, and AIUI doing the supported releases is blocked by doing trusty first. I've not had to deal with this before.
[14:51] <JackYu> infinity: hi, I have added some comments on bug #1293299 :)
[14:51] <ubot2> Launchpad bug 1293299 in Ubuntu Kylin "[FFE]upload ubuntu-kylin-software-center into archive" [High,Confirmed] https://launchpad.net/bugs/1293299
[15:06] <seb128> ^ I've pushed that ido update, please ping me if you have questions about it
[15:06] <seb128> it includes https://code.launchpad.net/~larsu/ido/basic-menu-item/+merge/213037
[15:06] <seb128> which is a bit of code changes (new widget basically)
[15:06] <seb128> I consider it as a bugfix and not a feature (it's basically support for non-squared icons to use in indicator-power/desktop only)
[15:07] <seb128> I'm open to discuss it if people think it's border line, but please ping me before eod if you want to discuss it ;-)
[15:07] <ahasenack> I guys, I uploaded a fix for https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1293990 to trusty-proposed, wondering what the next step is. Should I subscribe the release team to the bug?
[15:07] <ubot2> Launchpad bug 1293990 in landscape-client (Ubuntu Trusty) "error: config file /etc/landscape/client.conf can't be read" [High,In progress]
[15:09] <seb128> ahasenack, it has already been accepted, you should have received email?
[15:09] <seb128> ahasenack, or subscribe to trusty-changes
[15:09] <ahasenack> seb128: I got an email about it being accepted into trusty-proposed
[15:09] <ahasenack> is that it?
[15:09] <seb128> right
[15:10] <seb128> yes, same as usual
[15:10] <ahasenack> ah, cool
[15:10] <ahasenack> thanks
[15:10] <ahasenack> ah, ok, I got two
[15:10] <seb128> it's going to migrate to trusty once it has built/if it's installable and doesn't fail tests
[15:10] <seb128> well, we are frozen
[15:10] <ahasenack> first one was waiting for approval, the other one was accepted
[15:10] <ahasenack> ok
[15:10] <seb128> so it goes to "unapproved" first
[15:10] <seb128> then it gets accepted to proposed
[15:10] <seb128> which is basically what you directly get with upload in nonfreeze times
[15:10] <ahasenack> seb128: thanks for the explanation
[15:10] <seb128> yw!
[15:11] <ahasenack> and I see a bot here make sure such things are announced ;)
[15:20] <zul> stgraber:  https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1299055
[15:20] <ubot2> Launchpad bug 1299055 in openstack-trove (Ubuntu Trusty) "Icehouse tracker for rc1" [Undecided,New]
[15:22] <seb128> do you guys consider https://bugs.launchpad.net/indicator-power/+bug/880881 as a feature/needing a ffe?
[15:22] <ubot2> Launchpad bug 880881 in indicator-power "[ffe] Power indicator does not combine multiple battery status" [Medium,In progress]
[15:22] <seb128> or a bugfix?
[15:24] <stgraber> sounds like a bug to me
[15:25] <Laney> I guess it's debatable, but it's fine to get in imho
[15:25] <seb128> stgraber, Laney: thanks, I'm getting it in a silo then
[15:29] <seb128> thanks to whoever is reviewing/approving those ;-)
[15:31] <doko> stgraber, infinity: could you point ubuntustudio and lubuntu maintainers to the ftbfs at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140307-trusty.html ?
[15:31] <stgraber> I've done a few of those but I suspect Laney is also doing some of those
[15:31] <Laney> Nein
[15:31] <stgraber> zequence: ^
[15:32] <Laney> Someone else can have the credit for the recent ones
[15:32] <cjwatson> seb128: trying to keep on top of things, although I infer it isn't just me
[15:32] <stgraber> ah, so that was cjwatson then :)
[15:32] <cjwatson> yep
[15:32] <stgraber> cjwatson: yeah, I've noticed we collided at least a couple of times ;)
[15:33] <cjwatson> I noticed lxc's changelog referenced a bug without an lxc task on it
[15:33] <cjwatson> you still have time to fix that if you want to ...
[15:33] <seb128> cjwatson, stgraber: thanks ;-)
[15:33] <cjwatson> queue clear for now
[15:34] <stgraber> cjwatson: task added
[15:34] <cjwatson> thanks
[15:40] <zul> sorry can a release team member ack: https://bugs.launchpad.net/bugs/1299055
[15:40] <ubot2> Launchpad bug 1299055 in openstack-trove (Ubuntu Trusty) "Icehouse tracker for rc1" [Undecided,New]
[15:55] <jdstrand> that ^ is for oxide landing
[15:58] <stgraber> jdstrand: things that are only on the touch image get auto-approved
[15:58] <jdstrand> yeah, I forgot
[15:59] <jdstrand> thanks
[16:20] <slangasek> jibel: hi, so doko is telling me that the libffi that made it into the trusty release pocket overnight had broken revdep autopkgtest runs, but migrated anyway
[16:20] <slangasek> jibel: this seems like a significant bug, do you think this is something we should dig into today before the trail gets too cold?
[16:20] <seb128> slangasek, from earlier on #ubuntu-desktop
 pitti, seb128 I found at least 2 problems: libffi has been copied before britney received all the results of packages depending on it 2. Some results are marked as PASS while the result file contains a FAIL.
[16:21] <seb128> slangasek, you might still want to hear from jibel for specifics/bug reports ;-)
[16:21]  * slangasek nods
[16:22] <seb128> slangasek, btw how did that libffi landed during a freeze without a ffe?
[16:23] <slangasek> seb128: because according to doko, it was a bugfix-only release
[16:24] <seb128> hum, k ... the ChangeLog seemed a bit non-bugfix-only to me, but I guess it's at the appreciate of whoever reviewed it in unapproved
[16:24] <slangasek> seb128: right, AIUI the features were already in distro patches
[16:24] <seb128> k
[16:25]  * slangasek wonders why that discussion was on-topic for #ubuntu-desktop, two QA team members discussing a package that the foundations team maintains ;p
[16:26] <stgraber> slangasek: any chance I can get you to look at bug 1297363? seems like everyone else is scared of it or something :)
[16:26] <ubot2> Launchpad bug 1297363 in systemd (Ubuntu) "[FFe] Add cgmanager support" [Undecided,New] https://launchpad.net/bugs/1297363
[16:26] <slangasek> jibel: would be interested to know if you've found anything out about these britney bugs - or do you need us (e.g. cjwatson) to pick that up?
[16:26] <slangasek> stgraber: ohh.... ok
[16:27] <seb128> slangasek, it's started by a "why is update-manager not starting" question from me to pitti
[16:27] <slangasek> :)
[16:28] <seb128> but yeah, we should have changed channel then (though the issue was already discussed/handled by pitti before I started my day, it was mostly me catching up then)
[16:28] <doko> seb128, it has the new ports integrated, include aarch64 and ppc64
[16:29] <seb128> doko, well, that's fine, I was just surprised to see no bug reference/ffe ... and to see update-manager not starting anymore (= no way for normal users to get the bugfix version)
[16:30] <seb128> on that note, time for some exercice, bbl
[17:04] <slangasek> stgraber: systemd ffe approved; I also have a change to push for bug #1295521, can I rely on you to pick it up from lp:ubuntu/systemd when you upload?
[17:04] <ubot2> Launchpad bug 1295521 in systemd (Ubuntu) "Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break" [Undecided,Incomplete] https://launchpad.net/bugs/1295521
[17:04] <stgraber> slangasek: yep
[17:05] <slangasek> stgraber: ok, pushed my changes there
[18:00] <bdmurray> slangasek: I think arges is ready to join the ubuntu-sru team.
[18:10] <slangasek> infinity, cjwatson: ^^ do we want to give him a final exam before adding him? :)
[18:12] <cjwatson> slangasek: I'm happy to go with Brian's judgement
[18:17] <zequence> doko: Thanks. I'll look into it (I'm the Ubuntu Studio project lead)
[18:24] <slangasek> infinity: cjwatson and I are both happy with adding him on, so if you want to put him through the wringer you'll have to do it live ;)
[18:25] <arges> slangasek: i'm not in any hurry so i'm happy to answer questions whenever its convenient for everybody or even via email
[18:26] <slangasek> arges: too late, welcome to the SRU team!  Can we give you a day in the rotation? :)
[18:26] <arges> slangasek:  : ) Sure thing!
[18:26] <slangasek> let's see, which of us is doing the worst job of keeping up with their SRU day
[18:26] <slangasek> it might be me
[18:27] <slangasek> cjwatson: how are Wednesdays going, SRU-wise?
[18:28] <seb128> nice to see some new SRU manpower, LTS coming, which means piles of SRUs to handle ;-)
[18:28] <slangasek> quite
[18:30] <seb128> I'm still wanting to help if you guys are still interested btw (sorry, I said I would "candidate" some months ago but holidays have been in between and I dropped the ball on that)
[18:36] <arges> slangasek: so i'm cool with any day to help out. Let me know what day works best.
[18:41] <slangasek> ack
[19:20] <zul> cjohnston:  ping https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1299055
[19:20] <ubot2> Launchpad bug 1299055 in openstack-trove (Ubuntu Trusty) "Icehouse tracker for rc1" [Undecided,New]
[19:20] <cjohnston> zul: I'm guessing you mean cjwatson
[19:21] <zul> yes sorry
[19:21] <zul> cjwatson: ping https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1299055
[19:21] <ubot2> Launchpad bug 1299055 in openstack-trove (Ubuntu Trusty) "Icehouse tracker for rc1" [Undecided,New]
[19:33] <infinity> slangasek: Fine by me, I trust he was thoroughly trained and abused.
[19:33] <slangasek> ack
[19:36] <mlankhorst> choo choo
[20:22] <cjwatson> zul: I'm EOW now, sorry
[20:22] <cjwatson> slangasek: *cough* not been happening a whole lot, just now and again :-/
[20:39] <slangasek> cjwatson: oh no, this is horrible!  That means I have competition for the title of "least responsible SRU team member", and I can't just give arges my day!
[20:40] <cjwatson> I was assuming you'd just exercise your management privileges and instruct me to pull my finger out
[20:41] <slangasek> o right
[20:41] <slangasek> cjwatson: plz stop slacking
[20:41] <cjwatson> yers marster
[20:42] <cjwatson> the verification queues are pleasingly non-terrible at the moment
[20:43] <cjwatson> good work by people clawing those down
[20:44] <cjwatson> anyone want to confirm that they don't think anything in http://www.openssh.com/txt/release-6.6 really looks like it needs an FFe?
[20:44] <cjwatson> (er, yes, I actually am kind of EOW, this is really Debian work)
[20:45]  * cjwatson goes off to supervise children's bathtime
[20:46] <infinity> cjwatson: It looks fine, though I'm having a hard time parsing what the second bullet point in the feature/changes section actually means.
[20:52] <zul> slangasek:  ping https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1299055
[20:52] <ubot2> Launchpad bug 1299055 in openstack-trove (Ubuntu Trusty) "Icehouse tracker for rc1" [Undecided,New]
[20:54] <slangasek> zul: what's the question?
[20:55] <zul> slangasek: can i get an ack for the icehouse rc1 from the release team?
[20:55] <slangasek> ok, so this is an FFe request?
[20:55] <zul> yes
[20:57] <slangasek> zul: your bug description is far too high-level to be useful input to an FFe review.  Do you have pointers to debdiffs, or can you please include information about the features inline in the bug description?
[20:58] <slangasek> zul: also, what kind of analysis have you done so far of the risks of updating?
[21:00] <zul> slangasek: no I dont have debdiffs since some of them are still blocked, we have done the testing in the openstack-ci as usual we are ok with the updates
[21:00] <slangasek> blocked on what?
[21:01] <zul> slangasek:  blocked on a database fix getting upstream which will be fixed in the rc1 when its out
[21:01] <slangasek> and if some things are blocked, does that mean they also aren't tested yet?
[21:01] <zul> slangasek:  we do per-commit testing in the openstack-ci lab like we did in saucy
[21:03] <zul> gaughen: ^^^
[21:04]  * gaughen reads
[21:05] <slangasek> zul: ok, so I suppose I could give a standing FFe for icehouse, provided that the packages continue to be tested via openstack-ci before upload
[21:05] <slangasek> but it certainly doesn't make sense for me to FFe approve rc1 by itself, before it's out
[21:05] <zul> slangasek:  cool thanks
[21:06] <zul> they always have been
[22:04] <slangasek> infinity: fyi, upgrading to trusty claims that trusty is still in alpha.  Something missed from the checklist?
[22:08] <infinity> slangasek: What claims that?
[22:08] <slangasek> infinity: the release notes displayed in update-manager
[22:10] <slangasek> bdmurray: you probably know where to change this, right?  Somehow I don't see it listed on https://wiki.ubuntu.com/BetaProcess
[22:10] <infinity> Yeah, this might be some special IS-mirrors static copy of the release notes...
[22:11] <infinity> I thought alphas and betas were meant to just grab the wiki version directly.
[22:11] <infinity> (Or, rather, the static copy isn't meant to exist, but to just be a redirect)
[22:11] <slangasek> infinity: I think it's a static HTML file that we push in the archive tree, or onto changelogs.ubuntu.com
[22:12] <infinity> Oh, http://archive.ubuntu.com/ubuntu/dists/trusty/main/dist-upgrader-all/current/DevelReleaseAnnouncement.html
[22:12] <slangasek> http://changelogs.ubuntu.com/meta-release-development -> yah that
[22:12] <infinity> So, I guess that needs a dist-upgrader upload to fix.
[22:13]  * infinity could have sworn there was something somewhere that reads the REAL release notes, not just the stub.
[22:13] <infinity> Maybe that's ubiquity that does that.
[22:13] <slangasek> yes
[22:15] <infinity> slangasek: http://paste.ubuntu.com/7171001/
[22:15] <infinity> slangasek: Seem reasonable?
[22:16] <infinity> It might make more sense to just rewrite that to be a generic "this is a development release" warning, so it doesn't need to be changed ever again, actually.
[22:17] <knome> highly approve that direction :)
[22:19] <infinity> Something like this http://paste.ubuntu.com/7171009/
[22:19] <infinity> slangasek: ^
[22:20] <infinity> Feels verbally redundant.  s/release/product/ maybe.
[22:20] <infinity> WHY AM I PUTTING THIS MUCH THOUGHT INTO THIS?
[22:21] <infinity> Someone give me an opinion that isn't my own, and I'll upload. :P
[22:22] <slangasek> why can't I just give you your own opinion?
[22:22] <slangasek> that sounds easier
[22:23] <slangasek> also, why can't you just cargo-cult from whatever was there last cycle? :)
[22:23] <slangasek> oh, because you're eliminating alphabeta
[22:23] <slangasek> infinity: s/pre-release //
[22:24] <infinity> slangasek: Y'think?  I didn't like the implication that we stop development after release (which we don't).
[22:24] <infinity> slangasek: Which is proof that I'm overthinking this string modification.
[22:24] <slangasek> post-release isn't development, it's perfection
[22:24] <slangasek> or something
[22:24]  * infinity snorts.
[22:25] <infinity> slangasek: Upload in the queue.
[22:26]  * infinity goes to commit to bzr to see if he just stomped over staged changes.
[22:26] <infinity> La la la.
[22:27] <slangasek> at least you got to it before I had to check ;)
[22:27] <infinity> Looks like I win.
[22:34] <bdmurray> all sorted then?
[22:35] <slangasek> aside from the queue not giving me a debdiff and making me review manually, yeah
[22:36] <bdmurray> I never thought I'd be excited for the kids to drive themselves but this is getting out of hand.
[22:44] <slangasek> bdmurray: they've got four feet between them
[22:44] <bdmurray> slangasek: I guess I walked back in the day, and I know they have experiencing walking / hiking.
[22:45] <bdmurray> Could somebody have a look at kerneloops for me?
[22:46] <slangasek> will do
[22:46] <bdmurray> thanks
[22:46] <slangasek> accepted
[22:47] <slangasek> bdmurray: is that going to suffice to get the data up somewhere we can get at it? Nothing's going to be marking bugs as dupes of the existing ones before the users have a chance to submit the data, is it?
[22:52] <bdmurray> slangasek: the retracer is marking them as duplicates after they are submitted to LP so we should be good.
[22:52] <slangasek> ok