[00:56] <SleepyJeremy> hello
[01:02] <geofft> you're a little late, if you were intending to show up for one of the sessions :)
[01:04] <SleepyJeremy> understood
[01:04] <SleepyJeremy> I was under a firewall when the session I was interested was on
[01:04] <SleepyJeremy> a.k.a. @work
[01:04] <SleepyJeremy> :)
[01:05] <SleepyJeremy> anybody on from the "Next steps for the click-package prototype for simplified app package installation" session? Or who knows about the app packaging model being proposed for ubuntu touch/phone?
[01:07] <geofft> You should be able to watch the video recording, from the summit page
[01:07] <geofft> and see the Etherpad notes.
[01:07] <geofft> #ubuntu-devel is probably a better channel to find folks
[01:08] <SleepyJeremy> ah ok
[01:09] <SleepyJeremy> I tried that before, kept being pushed into #ubuntu-touch which nobody is ever watching
[13:54] <zyga> hi
[13:55] <zyga> brendand: so you're leading this one as well>?
[13:55] <roadmr> hey!
[13:55] <brendand> zyga, indeed
[13:56] <brendand> seems this is starting in 3 mins
[13:57] <brendand> brb
[13:57] <zyga> brendand: ok, paste the hangout link when ready
[13:57] <roadmr> do we know who'll be helping us with the hangout and stuff?
[13:57] <bdmurray> I will
[13:57] <zyga-uds> bdmurray:thanks
[13:58] <roadmr> bdmurray: thanks! good morning!
[13:59] <spineau> Could someone paste the hangout url again?
[13:59] <spineau> please
[13:59] <brendand> bdmurray, paste the link here
[13:59] <roadmr> spineau: I don't think we have it yet
[14:00] <bdmurray> https://plus.google.com/hangouts/_/21d0b82e4f2532f0af0e595e8d62e13abb019da2?authuser=0&hl=en
[14:00] <spineau> roadmr: ok, I'm not late then :)
[14:09] <bladernr`> whats the link to the BP?
[14:10] <roadmr> https://blueprints.launchpad.net/certify-planning/+spec/foundations-1305-checkbox-release-process
[14:10] <bladernr`> thanks
[14:20] <jeffreyc> yes, CE QA is really happy with current process
[14:20] <bladernr`> can you join the hangout jeffreyc
[14:20] <bladernr`> https://plus.google.com/hangouts/_/21d0b82e4f2532f0af0e595e8d62e13abb019da2?authuser=0&hl=en
[14:43] <ara> hello
[14:44] <roadmr> ara: hi!
[14:44] <roadmr> ara: https://plus.google.com/hangouts/_/21d0b82e4f2532f0af0e595e8d62e13abb019da2
[14:45] <ara> roadmr, I will stay on IRC, for the 10 minutes that lasts
[14:45] <ara> but thanks :)
[14:45] <roadmr> ara: ok :)
[14:51] <ara> zyga, a schedule
[14:51] <ara> zyga, and when
[14:56] <spideyman> can I vote that we only put changes/bug fix note about checkbox core into the changelog? Remove the cruft of job and individual script updates?
[14:57] <ara> spideyman, that would never be accepted in Ubuntu
[14:58] <spideyman> meh...then we probably need to decouple them from checkbox.
[14:58] <ara> spideyman, yes, that I agree :)
[14:59] <cjwatson> You can still summarise changes in Ubuntu though; they don't have to be commit-level or anything
[15:00] <cjwatson> Or you could treat it as an upstream tarball, where we frequently have changes only in upstream changelogs/NEWS files or whatever and don't repeat them in debian/changelog
[15:00] <cjwatson> Various possibilities
[15:01] <roadmr> cjwatson: thanks!
[15:01] <zyga-uds> indeed, thanks
[15:02] <zyga> ara: what did you mean by 'a schedule and when'?
[15:02] <roadmr> ara: do you know how to go about scheduling another session for tomorrow?
[15:02] <cjwatson> starting up hangout now
[15:02] <cjwatson> roadmr: ask a suitable track lead
[15:02] <cjwatson> (may or may not be space)
[15:02] <roadmr> cjwatson: oh ok thanks :)
[15:03] <Riddell> afternoon
[15:03] <brendand> running sessions is tiring :)
[15:04] <cjwatson> Kubuntu/UEFI/LTS hangout: https://plus.google.com/hangouts/_/6f16a08fd55e3e6db336ef84515052124bef0e8f?authuser=1&hl=en-GB
[15:04] <ara> zyga, I meant scheduling the work to be done
[15:04] <zyga> ara: scheduling the packaging changes? ok
[15:05] <cjwatson> (should I expect Kubuntu folks in the hangout?  I'm not certain whether you have the google hangout plugin sorted and such)
[15:05] <cjwatson> ah, there
[15:07] <Riddell> txwikinger: ?
[15:07] <cjwatson> txwikinger,xnox: are you joining the hangout?
[15:07] <Riddell> apw subscribed too?
[15:07]  * apw is just watching
[15:08] <xnox> cjwatson: i'm watching from a libary. I can provide a pretty picture with a backdrop, but can't speak out loud.
[15:08] <xnox> =)
[15:08] <xnox> (unless I move elsewhere)
[15:08] <xnox> I'd rather chat on irc.
[15:09] <apw> cjwatson, i can see it
[15:09] <xnox> \o/
[15:09] <Riddell> http://blogs.kde.org/2013/05/09/breakouts-uefi
[15:10] <xnox> cjwatson: Riddell: isn't this more about SB, rather than just UEFI.
[15:10] <skellat> Any of you have working cameras?
[15:10] <cjwatson> I have mine turned off
[15:11] <cjwatson> I mean if you *really* want to see my ugly mug :P
[15:12] <Riddell> mine doesn't seem to work today
[15:12] <Riddell> xnox: about SB?
[15:13] <bubbly193> no camera here
[15:13] <bubbly193> unless it decides to work
[15:14] <xnox> well, reading the blog post, it is a bit confusing as to what happened there. i only ever always had a single efi partition =/
[15:14] <apw> b 43
[15:15] <cjwatson> Bug 1167622
[15:15] <udsbotu> Ubuntu bug 1167622 in linux (Ubuntu) "Cannot change EFI variables using efibootmgr (raring regression)" [Medium,Confirmed] https://launchpad.net/bugs/1167622
[15:15] <cjwatson> That bug seems to be the root cause of the Kubuntu failure here
[15:15] <cjwatson> I'm not sure why it didn't break Ubuntu as well
[15:15] <cjwatson> Could be related to Kubuntu not using a signed kernel, I suppose, which would mean it would be booted slightly differently
[15:16] <apw> cjwatson, we would indeed boot rather differently if we are not using a signed kernel
[15:17] <apw> bug 1178294
[15:17] <udsbotu> Ubuntu bug 1178294 in ubiquity (Ubuntu) "Install fails with Kubuntu 13.04 on UEFI system" [Undecided,Confirmed] https://launchpad.net/bugs/1178294
[15:18] <cjwatson> apw: can you comment on 1167622?  would that cause the precise symptom in 1178294?
[15:18] <cjwatson> the failure there seems to be "bricks system" rather than "causes set_variable to fail"
[15:18] <apw> May 9 16:52:54 kubuntu ubiquity: Can't access efivars filesystem at /sys/firmware/efi/efivars, aborting
[15:19] <apw> that implies we did not have any access to the efivars at all, perhaps as a result of the mode
[15:19] <apw> ie not being booted into via the efi entry point
[15:20] <apw> on the '50% full' issue for nvram there have been some re-re-re-fixing in the handling of sizes
[15:22] <cking> bug 1167622 gets an efi "EFI_OUT_OF_RESOURCES" error, so it looks like there is not enough free EFI NVRAM free
[15:22] <udsbotu> Ubuntu bug 1167622 in linux (Ubuntu) "Cannot change EFI variables using efibootmgr (raring regression)" [Medium,Confirmed] https://launchpad.net/bugs/1167622
[15:23] <apw> cking, that might be one of those corner cases the later kernels have worked round, where the firmware lies in some of the size responses
[15:23] <cking> yep, or just lame firmware that can't be worked around, hard to tell
[15:23] <apw> indeed
[15:28] <cjwatson> damn, lost my connection
[15:28]  * cjwatson attempts to reconnect but isn't hopeful
[15:29]  * cking notes any EFI status  8000000000000009 means there isn't enough variable space, but we are at the mercy of the EFI run time services so who knows why it really failed
[15:29] <apw> cjwatson, i think kernel concurs with your position, that we should get kubuntu using the signed kerenl and then review the remaining issues, the rest ought to be common to ubuntu as well
[15:29] <apw> Riddell, is it you who has the list of bugs found during the install, those should be in the pad
[15:31] <xnox> cjwatson: you did well =)
[15:31] <stgraber> cjwatson: looks good, same URL
[15:31] <Riddell> apw: I filed bug 1178294 for not working on my uefi/sb machine, is that what you mean?
[15:31] <udsbotu> Ubuntu bug 1178294 in ubiquity (Ubuntu) "Install fails with Kubuntu 13.04 on UEFI system" [Undecided,Confirmed] https://launchpad.net/bugs/1178294
[15:31]  * cjwatson tries to find apachelogger's bug
[15:33] <cjwatson> he said on 2013-05-02 that he was going to file one
[15:33] <apw> bug 1167622
[15:33] <udsbotu> Ubuntu bug 1167622 in linux (Ubuntu) "Cannot change EFI variables using efibootmgr (raring regression)" [Medium,Confirmed] https://launchpad.net/bugs/1167622
[15:36] <cjwatson> bug 1171099 - but on reflection it appears unrelated
[15:36] <udsbotu> Ubuntu bug 1171099 in kubuntu-settings (Ubuntu Saucy) "kubuntu - plymouth not shown" [High,Triaged] https://launchpad.net/bugs/1171099 - Assigned to Harald Sitter (apachelogger)
[15:36] <cjwatson> sorry for derailing, I was triggering mentally on "grub" and "kubuntu" :)
[15:38] <cjwatson> apw,cking: would one of you be a sensible kernel contact if there are still outstanding bugs?
[15:38] <apw> cjwatson, yeap poke me
[15:38] <cjwatson> definitely looks like the first step is "get saucy into gear and try it"
[15:38] <cjwatson> ok
[15:39] <apw> yep concur, i should have kit to test it with as well, at least a bit
[15:39] <cking> apw, as long as you don't brick it
[15:40] <apw> cking, i am sure i will
[15:41] <apw> cjwatson, there was a bug somewhere with all the changes connected to it i think, at least all the packages
[15:42] <cjwatson> Yeah, I remember that, though I fear it was incomplete
[15:42] <cjwatson> I'll hunt it down
[15:45] <cjwatson> Riddell: is there a blueprint for this, btw?  just asking 'cos if so it would decrease the chance of work items getting lost
[15:46] <Riddell> cjwatson: nope, shall I make one?
[15:46] <cjwatson> if you would that'd be great
[15:52] <Riddell> cjwatson: voila https://blueprints.launchpad.net/ubuntu/+spec/foundations-1305-kubuntu
[15:53] <cjwatson> ta
[15:55] <cjwatson> done the seed bits for saucy at least - precise will take more work
[15:55] <cjwatson> and probably ought to make sure first that it works in saucy, anyway
[16:02] <lool> hey
[16:03]  * pitti waves
[16:03]  * ogasawara waves
[16:03] <ogasawara> not sure if bdmurray or cjwatson is starting up our session
[16:04] <cjwatson> ogasawara: bdmurray
[16:04] <bdmurray> ogasawara: I should be just a moment
[16:04] <ogasawara> ack, thanks
[16:04] <cjwatson> we had a brief mix-up
[16:05] <ogasawara> https://plus.google.com/hangouts/_/d9954311986ea36d3861625cd022d9dc8db2c213?authuser=0&hl=en
[16:05] <ogasawara> lool, mfisch, sforshee ^^
[16:06] <ogasawara> pitti: ^^ if you feel inclined
[16:07] <apw> ogasawara, are we live yet ?
[16:07] <ogra_> doesnt look like
[16:07] <ogasawara> just starting
[16:08] <apw> not seeing it yet
[16:09]  * ogra_ sees ... 
[16:10] <ppisati> video stutters here...
[16:10] <ogra_> it didnt here until you said that !
[16:10] <ppisati> LOL :)
[16:11] <ogra_> :)
[16:12] <sforshee> http://goo.gl/KMlMv
[16:12] <mfisch> system power policy doc: http://goo.gl/KMlMv
[16:15] <rickspencer3> I like the mental model that it's a constant battle between the power manager trying to reduce power and apps trying to keep it
[16:16] <rickspencer3> so app authors have to do work to fight against the power manager
[16:16] <mfisch> right, via curated APIs
[16:16] <ogra_> yeah the api should help them
[16:18] <rickspencer3> yeah
[16:18] <rickspencer3> app authors have to wage battle against the power manager, but only through the api
[16:18] <rickspencer3> that means the power manager will have the deck stacked in its gavor
[16:18] <ogra_> tvyou are
[16:18] <rickspencer3> favor*
[16:20] <achiang> maybe google i/o is melting the internet now
[16:20] <mfisch> seth's video always freezes ;)
[16:21] <brendand> QUESTION: at what level will these inhibitors be 'switched on' as it were, such that all the responsibility doesn't lie with each individual app?
[16:21] <pitti> sforshee: yeah, I think I have like a 10 second lag, sorry
[16:21] <ogra_> funny conversation
[16:21] <brendand> e.g. why have each app that could play music switch it on, when the audio subsystem (pulse?) will know this anyway?
[16:22] <ogra_> brendand, well, tha ypi will switchi it on
[16:22] <ogra_> *the api
[16:22] <achiang> brendand: the responsibility is *below* the app level
[16:22] <achiang> brendand: the API backend will manage this on behalf of the apps
[16:22] <ogra_> i.e. your app plays music ... the api knows that and tells pulse about it
[16:22] <ogra_> and pulse inhibits
[16:22] <mfisch> brendand: the app calls playBackgroundMusic() and then the audio service/pulse tells power manager "dont suspend"
[16:23] <brendand> it seems that it should be inhibited at the lowest level possible that makes sense
[16:24] <mfisch> brendand: what do you mean?
[16:24] <achiang> brendand: the whole point of hiding it behind the API is precisely to inhibit at the level that makes sense
[16:24] <ogra_> pitti, it think we also want to live that stuff on a system level, not a session one ... logind could be our channel for conversation i guess though
[16:26] <pitti> ogra_: yes, I agree; you can query them at a system level, but they are still tied to a particular session/seat
[16:26] <pitti> (powerd wouldn't need to care about which particular session, of course)
[16:26] <ogra_> right
[16:26] <brendand> mfisch, i guess my question is answered. that was just a general observation
[16:27] <mfisch> ogra_: thats what we envisioned, logind is out path to match sessions and seats
[16:27] <ogra_> yeah
[16:27] <mfisch> sessions may request a display state and we need to map that to a physical display (seat) which in turn is managed by a system compositor
[16:27] <ogra_> did you guys look into teh existing powerd already
[16:27] <ogra_> ?
[16:28] <mfisch> ogra_: yes, we are currently coding some enhancements onto it to prove out the concepts
[16:28] <ogra_> awesome :)
[16:28] <brendand> question the second: how fine grained can the hardware control be? can it switch e.g. everything off but the wifi chip, or even vice versa?
[16:28] <ogra_> the kernel can ...
[16:28] <mfisch> brendand: we plan that PM only manages screen power and system power (suspend), but not, for example, low power wifi states
[16:28] <ogra_> so the question is how much use do we make of it
[16:29] <mfisch> if the wifi chip supports some low power mode, for example, the wifi stack deals with that
[16:29] <ogra_> (over time)
[16:29] <brendand> mfisch, that's true
[16:29] <cking> the devil is in the unexpected detail, so we need to start somewhere
[16:29] <mfisch> agreed
[16:30] <mfisch> just from starting to implement some stuff I've run into several questions about how the API would work
[16:30] <ogra_> he is currently doing it himself
[16:30] <ogra_> since he wrote the initial version
[16:31] <apw> ogasawara, damn straight
[16:31] <ogra_> sforshee, about time !
[16:32] <ogra_> kernels are boring ... userspace has all the excitiment
[16:32] <mfisch> Chicken: you've got me until friday ;)
[16:33] <brendand> mfisch, actually what i meant was that say the only thing that is happening on the system is a file download. what is the most efficient power state that can be reached?
[16:33] <sforshee> ogra_, I like kernels ;-)
[16:33] <ogra_> :)
[16:34] <mfisch> brendand: it depends on the system, realistically probably screen off but not suspended, however, if you had a system where you could download a file without the system CPU, then it would work like this
[16:34] <mfisch> (these are made-up API calls), app calls downloadBackgroundFile()
[16:34] <pitti> aren't ARM processors more flexible in that regard?
[16:34] <mfisch> then download manager decides whether the system should suspend or not
[16:34] <ogra_> a lot
[16:34] <mfisch> right
[16:34] <pitti> i. e. that they already shut down units which aren't necessary for a particular task?
[16:35] <ogra_> depends
[16:35] <sforshee> pitti, yes to some degree
[16:35] <lool> it's a whole system really
[16:35] <lool> on a single chip
[16:35]  * pitti really liked the OLPC which could display a static image with shutting down the CPU and GPU :)
[16:35] <ogra_> i.e. if the kernel (and HW) supports the interactive governor you can do very intresting things on that level
[16:35] <rfowler> QUESTION: when suspending the device via power button you should still be able to access a device via adb correct?
[16:35] <ogra_> very finegrained too
[16:36] <rfowler> because the nexus 10 doesn't
[16:36] <mfisch> rfowler: I thought on Android there's a wakelock held when you're using adb that prevents suspend
[16:36] <pitti> ogra_: can you run an ARM CPU at hilariously slow speeds? like 500 kHz or so?
[16:36] <sforshee> rfowler, yes, in that case the system should turn off the screen but not suspend
[16:36] <sforshee> rfowler, we don't have all the infrastructure in place yet ;-)
[16:36] <ogra_> pitti, heh, never tried below 200MHz
[16:36] <ogra_> pitti, i suppose it might work though
[16:37] <sforshee> mfisch, the nexus 10 kernel doesn
[16:37] <sforshee> doesn't have the same wakelock infrastructure as past android devices
[16:37] <mfisch> ah the n4 seemed to
[16:37] <mfisch> I dont have a n10
[16:37] <sforshee> n4 still uses the old android wakelock model
[16:37] <rfowler> thanks
[18:01]  * cjwatson gets back to the hangout creation dance
[18:02] <cjwatson> https://plus.google.com/hangouts/_/375a4beea5be9186d8db528da6728c294bddc025?authuser=1&hl=en-GB
[18:05] <cjwatson> anyone else joining the hangout?  It's rather quieter than I expected :)
[18:05] <cjwatson> rickspencer3: ^-
[18:05] <cjohnston> is it just you cjwatson ? ;-)
[18:06] <cjwatson> And stgraber
[18:06] <rickspencer3> hi cjwatson I'd be happy to join
[18:06] <rickspencer3> cjwatson, I don't know that I can contribute much technical, thouhg
[18:07] <cjwatson> Fair enough, thanks
[18:07] <cjwatson> https://plus.google.com/hangouts/_/375a4beea5be9186d8db528da6728c294bddc025?authuser=1&hl=en-GB
[18:09] <pumpichank> sorry, could someone please repost the hangout url?
[18:09] <balloons> https://plus.google.com/hangouts/_/375a4beea5be9186d8db528da6728c294bddc025?authuser=1&hl=en-GB
[18:09] <pumpichank> thanks
[18:14] <xnox> stgraber++
[18:14] <pumpichank> let's call it "sid" <wink>
[18:16] <apw> cjwatson, would we be able to upload to this new name, i am assuming not
[18:17] <stgraber> apw: no
[18:17] <stgraber> well, that's what Rick brought up, but the current plan is a simple symlink at the archive level
[18:17] <stgraber> LP wouldn't be aware of that
[18:19]  * xnox ideally wishes _all_ uploads to be phased in the devel release =)
[18:24] <balloons> the current qa community folks would be happy to run this :-)
[18:25] <cjwatson> apw: Rick brought it up and I hadn't thought about it; it's easy enough to do
[18:26] <cjwatson> stgraber: I was planning to have LP create the symlink, though (in the publisher)
[18:26] <cjwatson> pumpichank: iron rule: no name clashes with Debian :)
[18:26] <cjohnston> In the session before lunch we discussed how to display key performance indicators on the QA Dashboard that could be  helpful of people trying to decide to update
[18:27] <xnox> the bit that is missing, is the pop-up: 'wanna see the next ubuntu's wallpaper?' =)))))
[18:27] <xnox> cjohnston: KPI is an indicator, using a devel release should be more playful & impulsive. I think. If one looks at stability indicators, precise will always win.
[18:28] <chiluk`> I think the other fear is fear of hardware being killed by the development version...
[18:28] <cjohnston> xnox: sure, however if people are asking on IRC if they should update, that would give them something to look at
[18:29] <balloons> if they are asking to update or not, odds are they aren't good candidates :-)
[18:30] <xnox> I am somewhere between cjohnston & balloons, closer to balloons stance I think =)
[18:31] <cjohnston> I haven't switched yet, but I've thought about it.. partially due to time... but it would still be nice to see if today is looking ok before doing it
[18:31] <balloons> it is fair to ask/check if something is totally borked before upgrading.. but in general, your running the devel release for a specific reason. We hope your running it to help ubuntu itself out by testing, hacking, developing, whatever
[18:31] <cjohnston> that's what I'm getting at
[18:32] <balloons> cjohnston, however, I've never done such a thing.. If an upgrade fails, I file a bug
[18:32] <balloons> wait and try again ;-)
[18:33] <cjohnston> If you can look and see that its going to break and there is already a bug, why try
[18:34] <chiluk`> can't we get statistics like that by monitoring accesses to the development repos?
[18:34] <balloons> cjohnston, if there was a known issue, I would be more inclined to try :-)
[18:35] <balloons> it's about setting expectations for the release. I don't think anything has to really changed on that front. If your running -devel release things may break
[18:35] <balloons> it's all part of the experience, and to the extent you have an issue, report it, workaround it and move on
[18:37] <pumpichank> omgomega
[18:37]  * xnox .o0(now we just need a 7 grade scale of neo-users)
[18:38] <lool> "dev"
[18:38] <chiluk`> tip++
[18:39] <balloons> you could still call it rolling :-)
[18:39] <xnox> where is the marketing department when you need them? =))))
[18:39] <pumpichank> good thing there's no possibility of bikeshedding the name
[18:39] <pumpichank> rickroll
[18:39] <xnox> "fresh"?
[18:40] <xnox> let's call it "tumble weed".
[18:40] <balloons> preview?
[18:40] <xnox> warty?
[18:40] <TheMuso> lol
[18:40] <cjohnston> nonameyet
[18:40] <xnox> adjective and an animal? to put into lsb-release os / etc?
[18:41] <balloons> +1 nonamyet
[18:41] <chiluk`> rolling does already have a bunch of publicity out there.
[18:42] <cjohnston> nonameyet because Mark hasn't picked an animal
[18:42] <cjohnston> heh
[18:42] <plars> voyager
[18:42] <pumpichank> rolling is not bad
[18:43] <balloons> honestly rolling probably communicates things simply, without requiring more explanation
[18:43]  * apw suggests bikeshed
[18:43] <lool> +1
[18:43] <cjwatson> phk </obscure>
[18:44] <apw> lool, no no no, he wants one we cannot have without blowing LP up
[18:44] <lool> :-)
[18:44] <chiluk`> just blog about it
[18:44] <lool> plus it's probably (tm) google
[18:51] <chiluk`> that would be help those who are afraid to move early in the development release as well.
[18:53] <Laney> anything else here?
[18:53] <rickspencer3> thanks cjwatson
[18:53] <rickspencer3> I <3 "rolling" ;)
[18:53] <cjwatson> thanks everyone
[18:54] <chiluk`> rolling roadrunner  ...... acme flashbacks
[18:54] <cjwatson> rickspencer3: I'll drop this into the blueprint whiteboard/WIs, so maybe just edit there when I'm done rather than fighting with etherpad
[18:54] <balloons> rick rolling rash roadrunner
[18:54] <balloons> release
[18:54] <balloons> :-p
[18:54] <apw> rickspencer3, it hought you loved the rolling release, hiding it seems odd
[18:56] <cjwatson> ah, "export as plain text" from the pad => less unpleasant way to get it into blueprints
[18:56] <cjwatson> rickspencer3: all in the bp now
[18:56] <rickspencer3> cjwatson, ok, I'll pop my notes in there then
[19:01] <knome> hello
[19:02] <knome> who's running the hangout?
[19:02] <bdmurray> I am
[19:03] <knome> i suppose i'd like to join that one :)
[19:03] <knome> defining want in the "should" sense ;9
[19:04] <knome> elfy, o/
[19:04] <bdmurray> https://plus.google.com/hangouts/_/ef55fe3b04e56166a89aa6c2a748602a149da165?authuser=0&hl=en
[19:04] <elfy> knome: yep - I'm here
[19:04] <elfy> more or less
[19:05] <knome> :)
[19:05] <knome> oodie
[19:05] <knome> +g too (not g+)
[19:08] <xnox> is the feed live?
[19:08] <elfy> it's very quiet :p
[19:08] <elfy> xnox: not that I can see
[19:08] <apw> xnox, not here
[19:08] <bdmurray> just started it
[19:09] <plars> hear no evil, see no evil... not live yet
[19:09] <apw> bdmurray, there is a heck of a lag from the originators timezone to ones a ways away
[19:09] <stgraber> https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[19:09] <plars> ah, there it is
[19:09] <bdmurray> apw: are you suggesting I move?
[19:09] <balloons> ahh video :-)
[19:10] <apw> bdmurray, it is the obvious solution :)
[19:11] <xnox> cjwatson: there are bits on the pad to discuss =)
[19:12] <cjwatson> those were things I said
[19:13] <balloons> lol.. yes, milestones seem to be pretty good drivers for flavors
[19:13] <cjwatson> balloons: what was your sense of testing of earlier milestones?
[19:14] <xnox> cjwatson: i see =) lag.
[19:15] <balloons> in comparison to ubuntu, they were pretty tame. However, I do echo stgraber here. Flavors like kubuntu and lubuntu got there work done as part of having milestones; they seemed to like having that 'hard date' in which work needed to be complete
[19:15]  * elfy is listening - I'd agree with what knome has said 
[19:22] <xnox> in-dash payments.
[19:22] <xnox> was the other one, i think.
[19:27] <balloons> a2 and a3 being so close meant most flavors looking at it weren't going to do one of them :-)
[19:28] <cjwatson> yeah, I think that was among the reasons we deleted a3 from raring
[19:28]  * cjwatson harks back to the days of 7 alphas
[19:28] <knome> the proposed changes sound fine to me
[19:29] <knome> not me!
[19:29] <knome> way to go, mute all the community people >;)
[19:29] <balloons> +1 on making milestones ~= monthly cadence
[19:29] <cjwatson> :-P
[19:29] <cjwatson> unmute yourselves if you want to talk :)
[19:29] <knome> nah
[19:29]  * cjwatson is muted too
[19:30] <balloons> lol.. good practice so background noise of your cat doesn't pop in :-)
[19:30] <knome> oh, one can't see who's muted or not. interesting
[19:30] <knome> cat pooping in?
[19:30] <knome> i was told i type really loudly
[19:31] <balloons> will ff be moved back again?
[19:31] <balloons> I know there was still some drama even with it moved so far back into the cycle
[19:32] <cjwatson> you're the first person who's expressed a desire to move it back :)
[19:32] <cjwatson> want to expand?  as stgraber was saying, for once it seems to have been sort of successful
[19:33] <cjwatson> in that we didn't actually have too many major disruptive changes after FF
[19:33] <knome> depends on the release team i suppose
[19:33] <balloons> cjwatson, I think I confused everyone.. aka.. it's week 17, will it be week 20 in saucy like raring or no?
[19:34] <balloons> I speaking of feature freeze ^^
[19:34] <cjwatson> right, yeah, like we said there are a bunch of changes we made in raring that don't seem to have been mirrored into saucy
[19:34] <balloons> ok.. right, excellent
[19:34] <cjwatson> basically because there was an incredibly unwise decision several releases ago to create a bunch of release schedules in advance
[19:34] <cjwatson> so now we have to keep remembering to mirror changes ...
[19:35] <cjwatson> Adam took an action to push things over
[19:35] <balloons> lol.. you try and make less work for yourself, and boom
[19:36] <elfy> tring to remember last time that worked for me
[19:39] <balloons> mm.. adam, that's the point of cadence testing
[19:43] <balloons> fyi, if your curious of stats for raring; http://91.189.93.58/ scroll down to the "Raring Image Testers" and "Raring Image Results"
[19:43] <balloons> you can see the spikes are the milestones
[19:44] <balloons> the later milestones had much more traction than the early milestones
[19:48] <knome> adam should use xfce ;)
[19:48] <balloons> use google dns :-p
[19:51] <knome> can you also mail the flavor devel lists?