17:08 <popey> #startmeeting Clock meeting
17:08 <meetingology> Meeting started Thu Oct  9 17:08:52 2014 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:08 <meetingology> 
17:08 <meetingology> Available commands: action commands idea info link nick
17:08 <popey> Hows it going?
17:08 <nik90> popey: hello
17:09 <nik90> great :)
17:09 <popey> hi rpadovani also, thanks for helping nik90 on the clock!
17:09 <nik90> frantically merging all the MPs today
17:09 <popey> so i see ☻
17:09 <popey> my inbox is enjoying it
17:09 <nik90> :)
17:09 <rpadovani> yw :-)
17:09 <nik90> I was blocked by jenkins, and I want to really release clock tomorrow
17:10 <popey> Is that unblocked now?
17:10 <nik90> once I am done with all the merges, I will create a click and perhaps you can test it for overall quality?
17:10 <nik90> yes francis and balloons unblocked it today
17:10 <popey> sure thing!
17:10 <popey> will that be later today?
17:10 <nik90> most likely
17:11 <popey> ok, no problem
17:11 <nik90> I will be running the manual test suite tomorrow morning as per elopio's request before every landing in store
17:11 <popey> seems jenkins is taking a while to autoland?
17:11 <nik90> yeah seems like it. Took 20+ mins
17:12 <nik90> but I shouldn't complain, considering jenkins atleast passes now
17:12 <popey> heh
17:13 <nik90> I have been keeping an active eye on the ubuntu-rtm silos, and it looks like a stream of location fixes are coming in still.
17:13 <nik90> I will wait for them to land before checking my location MP.
17:13 <popey> ok.
17:14 <nik90> meanwhile I need to take care of this alarm audio channel role bug https://bugs.launchpad.net/bugs/1362078
17:14 <popey> location still doesn't seem fully baked
17:14 <nik90> yeah :/
17:14 <nik90> and I don't want to push something not fully baked into clock
17:16 <popey> was just reading the internal channel about location, seems there's still some issues.
17:16 <popey> so I'd certainly hold that for a while longer
17:17 <nik90> I will wait for maybe 1-2 weeks after which I am going to postpone this to OTA. I am a bit worried about introducing something as big as my location MP this late.
17:17 <popey> I know they're working with HERE to get it all nailed
17:17 <nik90> it would be kinda awkward to see "Location Service Error" if not done correctly
17:18 <popey> seems quite a bit of work going on there, so I'd like to hope it's finished sooner, but obviously no guarantees.
17:18 <popey> yes
17:18 <nik90> we will re-evaluate again next week
17:18 <popey> +1
17:18 <nik90> I am hoping to also get some performance patches in this weekend. So next week should be fun :)
17:19 <nik90> and in the MPs we are landing today, I have added qml unit tests for pretty much every alarm function we use. So if something in alarm goes wrong, we will know immediately if clock app is at fault or whether it is upstream
17:19 <popey> ooh!
17:19 <popey> Nice work!
17:20 <popey> We have a long running bug that only a few people have reproduced, well, only one so far
17:20 <popey> where the alarm sometimes doesn't trigger
17:20 <popey> I haven't seen this myself, my alarm goes off every day.
17:20 <popey> I know charles is looking into it.
17:20 <nik90> hmm, I asked saviq and he said the alarm didn't go off for him once but was fine after that
17:21 <popey> i had the alarm go off one minute late recently
17:21 <popey> but it happens when I'm half asleep (naturally) so sometimes I think I'm dreaming when it happens
17:21 <nik90> yes that has to be indicator-datetime not updating the time correctly while being suspended
17:21 <popey> need to set more alarms through the day to a) annoy everyone, b) test better
17:21 <nik90> as a result it misses a few seconds
17:22 <popey> right
17:22 <nik90> I believe zsombor is working on this huge patch for the alarms backend. I am not sure yet why he is doing that now, but I will be checking in tomorrow about it.
17:23 <nik90> as far as I can see, the alarm backend which currently relies on EDS will be removed post-rtm since EDS is just too heavy.
17:23 <popey> Hmmmm
17:23 <nik90> ofcourse it is still being discussed at the moment
17:23 <popey> yet we use EDS for calendar too
17:23 <popey> this could have wider implications
17:23 <nik90> yeah and that's causing conflicts and confusion
17:23 <popey> ok
17:24 <nik90> clock alarms are being mixed with calendar events in indicator-datetime
17:24 <nik90> I don't think EDS will be removed from the phone
17:24 <nik90> just that clock alarms won't use it
17:24 <popey> right
17:24 <nik90> again this is not something for the near future..so we got to think carefully and see how it turns out.
17:25 <popey> yeah.
17:25 <popey> On another subject..
17:25 <popey> are you adding a splash to clock?
17:25 <nik90> I have informed Girgio about it and waiting on a reply
17:26 <nik90> since Clock doesn't have a header, it might look a bit awkward to just show a white page for the splash screen
17:26 <popey> yeah
17:26 <popey> clock and calculator are the exceptions
17:26 <nik90> ah yes..calculator as well
17:27 <popey> was suggested we just have a blue screen
17:27 <popey> not sure i like that
17:27 <nik90> I will start an email thread with giorgio and cc you and jounih to it.
17:28 <popey> thanks
17:28 <popey> Ok, anything else?
17:29 <nik90> nope, me and charles are trackign the alarm bug at https://blueprints.launchpad.net/ubuntu-clock-app/+spec/alarms-rtm
17:29 <nik90> in case you see a bug not there, let me know
17:29 <nik90> that should put it in our radar
17:29 <nik90> that was it
17:30 <popey> ok
17:30 <popey> magic
17:30 <popey> thanks guys.
17:30 <popey> ping me if I'm afk and I'll do some testing
17:31 <popey> telegram is fine too :D
17:32 <popey> s/telegram/webogram/ ☻
17:32 <popey> #endmeeting