== Meeting information ==
 * #ubuntu-touch-meeting: clock app meeting, 24 Apr at 17:09 — 17:30 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2014/ubuntu-touch-meeting.2014-04-24-17.09.log.html]]



== Meeting summary ==




== Vote results ==




== Done items ==

 * (none)



== People present (lines said) ==

 * popey (67)
 * nik90 (37)
 * meetingology (3)



== Full Log ==


 17:09 <popey> #startmeeting clock app meeting

 17:09 <meetingology> Meeting started Thu Apr 24 17:09:53 2014 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 17:09 <meetingology> 

 17:09 <meetingology> Available commands: action commands idea info link nick

 17:10 <popey> Clock App links:-

 17:10 <popey> Bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs

 17:10 <popey> Reviews: https://code.launchpad.net/ubuntu-clock-app/+activereviews

 17:10 <popey> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/coreapps-1404-clock-dev

 17:10 <popey> General Links:-

 17:10 <popey> Milestones: https://launchpad.net/ubuntu-phone-coreapps/+milestones

 17:10 <popey> Burndown: http://status.ubuntu.com/coreapps-14.04/

 17:10 <popey> Blockers: https://wiki.ubuntu.com/Touch/CoreApps/Blockers

 17:10 <popey> how are you nik90 ?

 17:10 <nik90> good..busy with the showdown

 17:10 <nik90> and yourself?

 17:11 <popey> Great! Now the release has passed, we have lots to do! :D

 17:11 <nik90> yeah :)

 17:11 <nik90> just waiting on the U-archive to open up

 17:12 <popey> Yeah, should be monday/tuesday

 17:12 <nik90> What a code name Utopic Unicorn

 17:12 <popey> heh, yeah ☻

 17:12 <popey> with a test image from ogra early that week assuming cjwatson can get a server image built

 17:12 <nik90> ok..I created some new milestones for this cycle

 17:12 <popey> awesome.

 17:12 <nik90> I still need to sit down and plan what needs to be done when

 17:13 <nik90> do we have a new blueprint?

 17:13 <popey> Right, on that subject..

 17:13 <nik90> for this cycle?

 17:13 <popey> Not yet.

 17:13 <popey> We are going to have a slightly different release cycle this time

 17:13 <nik90> oh

 17:13 <popey> because we'll be focussed mostly on the phone manufacturer release to manufacturer date

 17:13 <popey> rather than the 12.10 traditional release date

 17:13 <popey> as they are not the same.

 17:13 <popey> uh, 14.10

 17:13 <nik90> ah ...makes sense.

 17:14 <popey> I don't actually have a final date though.

 17:14 <nik90> When is the expected phone manufacture release dates that we need to target

 17:14 <popey> Which makes working backwards somewhat tricky

 17:14 <nik90> do we have atleast a month decided?

 17:14 <popey> However I think we need to be aiming to be _done_ by ~July.

 17:14 <popey> So it's a short cycle.

 17:15 <nik90> wow that's 3 months give or take

 17:15 <popey> Yup.

 17:15 <popey> The good news is most of the apps are "done"

 17:15 <popey> (for some value of "done")

 17:15 <nik90> true

 17:15 <popey> I'm also trying to get a definitive list of what the expectations are for that build

 17:16 <popey> whether we expect a world clock for example

 17:16 <popey> or whether we expect a full redesign or something

 17:16 <nik90> we need to nail the alarms first asap

 17:16 <popey> +1

 17:16 <popey> that should be where all the attention goes right now

 17:17 <popey> making sure alarms work, the times are right, timezones and daylight savings, and year rollovers are all taken into account

 17:17 <nik90> I will create a milestone which has all the alarm bugs we know up to date and then start fixing them one by one

 17:17 <popey> Great!

 17:17 <popey> We may need to do some edge case testing

 17:17 <nik90> you were referring to the timezones and daylight savings of the alarms and not the world clock right?

 17:17 <popey> forcibly setting the date to strange values on device to test edge cases

 17:17 <popey> correct

 17:18 <nik90> because for the world clock that would be more work than I can expect to get done in 3 months. Plus I need some help from the SDK devs for that

 17:18 <popey> We don't want to have an article like this www.tuaw.com/2014/03/08/daylight-saving-public-service-announcement-dont-count-on-your/

 17:18 <popey> world clock was just me throwing things out that I dont know ☻

 17:18 <popey> consider it an unknown unknown

 17:18 <nik90> +1 to the article :)

 17:19 <popey> I want us to be confident that alarms will trigger when users expect them to

 17:19 <nik90> yes

 17:19 <popey> So I think we need a test plan for all those strange cases

 17:20 <popey> for example testing by people in different timezones, alarms set for weekdays, weekends, alarms set on the day after daylight savings

 17:20 <popey> some will be hard to test, but we need to figure a way. could be a good discussion at Malta

 17:20 <nik90> yeah. I think we need to first define all the edge cases. Only then we can test them and create AP tests for them

 17:20 <popey> ya

 17:20 <nik90> definitely

 17:22 <popey> Any other things to consider?

 17:22 <nik90> I will let you know when I get the milestone, wiki doc for the edge cases and other stuff ready. I guess I have some todo this weekend

 17:22 <popey> Ok.

 17:22 <nik90> btw phones are high priority at the moment for the cycle right? or do we still need to do some tablet designs

 17:23 <nik90> I remember mark saying that tablets would land at the same time

 17:23 <popey> Phone is #1

 17:23 <nik90> ok

 17:25 <nik90> that was it from my end

 17:25 <popey> With U and the SDK changing under our feet, there's the possibility of things breaking now and then again.

 17:25 <popey> So we need to be certain we have great tests

 17:25 <nik90> oh yeah .. the tab bar changes

 17:25 <popey> so we can be sure when something breaks the finger of blame can't come our way ☻

 17:25 <popey> yeah

 17:25 <nik90> luckily we use the toolkit emulators..so I know who to blame :P

 17:25 <popey> hah

 17:25 <nik90> luckily -> well planned efforts by elopio

 17:26 <popey> Of course it's not about blaming people but making sure we don't hold up the train with unnecessary debugging

 17:26 <popey> I expect a Qt5.3 tranition at some point too

 17:26 <nik90> yeah..btw the alarm status bug we had last week was due to the EDS...I believe renato has a Mp for it.

 17:27 <popey> Yeah. Brilliant.

 17:27 <popey> I didn't have anything else. All set for Malta?

 17:27 <nik90> I didnt get a reply. So I sent the email again to the travel agent

 17:27 <popey> ooh, please do as a matter of urgency.

 17:28 <nik90> if I don't hear by tomorrow, I will email Michelle

 17:28 <popey> if you get no response, michelle can help

 17:28 <popey> Wouldn't want us to miss out on having you there.

 17:29 <nik90> yeah ..I will ensure this is done by next week

 17:29 <popey> (or you to miss out on our delightful company ㋛

 17:29 <popey> Ok, that's all from me.

 17:29 <nik90> hehe

 17:29 <nik90> me too

 17:29 <popey> thanks as always nik90 ☻

 17:29 <popey> take care.

 17:30 <popey> #endmeeting



Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)