17:01 #startmeeting Clock App meeting 17:01 Meeting started Thu Jan 16 17:01:50 2014 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:01 17:01 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 17:01 Clock App links:- 17:01 Bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs 17:01 Reviews: https://code.launchpad.net/ubuntu-clock-app/+activereviews 17:02 Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/coreapps-1404-clock-dev 17:02 General Links:- 17:02 Milestones: https://launchpad.net/ubuntu-phone-coreapps/+milestones 17:02 Burndown: http://status.ubuntu.com/coreapps-14.04/ 17:02 Blockers: https://wiki.ubuntu.com/Touch/CoreApps/Blockers 17:02 I'll take a look at https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-alarm-analogue-format/+merge/201282 after the call. 17:02 sure 17:03 I also asked zanetti to review it when he has time 17:03 ah okay 17:03 i have time after this call. 17:04 yeah definitely. I want to hear about your experience using it on the phone. 17:04 k 17:04 We spoke to tstrehl 17:04 about alarms 17:05 implementing the api seems to have been pushed back a week 17:05 david told me yesterday about the planned release to be in week 5 17:05 ah okay 17:05 yes, that's what I was going to mention 17:06 I think that's fine as long we get a date fixed 17:06 current work ongoing with the indicator, alarms service to follow after 17:06 as with all these things it's a big list of things to do this cycle 17:06 true 17:06 the good news is we're at the top of that list 17:06 :) 17:06 so unless some urgent show-stopper comes along we should be fine for the timescales david mentioned 17:07 do you want to hold off any clock releases to store until then? 17:07 #info Indicator-datetime fix planned for week 5 17:07 yes 17:07 ok. 17:07 I want to bring in more fixes to it before pushing an update out to the store 17:07 np 17:08 this week I also added a setting ui to switch between 12/24 hour mode. This also uses u1db to store it 17:08 oh neat 17:09 * popey looks at the blueprint 17:09 not much to update there. 17:09 #action nik90 Talk to zsombi about the Alarms API bug fixes 17:09 * meetingology nik90 Talk to zsombi about the Alarms API bug fixes 17:10 I just updated it yesterday I think 17:10 ah, okay 17:10 and the keyboard shortcuts work is also coming nicely 17:10 so overall this week was quite productive 17:11 yeah, I was impressed with how quickly that came together 17:11 also lots of conversations with the music app guys about u1db 17:11 I think I am a bit lucky that the bugs blocking u1db in music app wouldn't affect clock app 17:12 indeed 17:12 so I am slowly planning to transition other parts to u1db when possible 17:13 Ok. 17:13 Anything else? Blockers? 17:13 (other than already discussed)( 17:14 Next week however I will be busy with University stuff. So I will try to get things into the trunk by this week. 17:14 ok. 17:14 I would consider cancelling next week's meeting alone since I won't have much to report about due to it. 17:15 regarding the performance blocker bug, timp has fixed it. It just need a review and merge to trunk. 17:15 Although I am afraid that if I utilise that fix to do performance optimizations, then the clock app might break on the phone 17:16 since the SDK package on the phone is nearly 2 months old 17:16 due to the Qt 5.2 transition 17:17 hm 17:17 i know timo has a ppa with the qt5.2 stuff in already 17:17 and I expect at some point soon we will start agressively testing apps on 5.2 17:18 we can of course use the emulator for it 17:18 balloons: do you know what plans we have for testing apps on 5.2? 17:18 true but should I wait until the SDK package on the phone is updated before pushing the performance fixes to trunk? 17:18 i would, yes 17:19 currently looking at why clock is randomly failing on maguro 17:19 on 5.2? or current? 17:20 balloons: yup just had a look at your email 17:20 popey, I believe 5.2 is delayed till post 14.04? I am mistaken 17:20 oh! 17:20 balloons: what? 17:20 am i mistaken? lol 17:20 thats news to me! 17:20 * nik90 hopes not :/ 17:21 yeah, i dont think that's the case. 17:22 ok, checked 17:22 popey: can you confirm that later? It is quite important. 17:22 plan is feb/mar 17:22 lots of discussions 17:22 but thats the current plan 17:22 okay 17:22 yes, I checked as well.. last mailing indicate the push is still on.. So I am mistaken 17:23 \o/ 17:23 so yes, I'd hold back nik90 until 5.2 at end of feb. 17:23 the uitk has been tested against 5.2. there was some breakage.. I should ask leo about it 17:23 that's the big piece. I hope that will ease the transition for many apps 17:23 popey: okay 17:24 popey: in that case, I will focus on my efforts on digital style and u1db transition until then. 17:24 awesome. 17:24 #action nik90 Enquire with michael spencer about his convergence branch 17:24 * meetingology nik90 Enquire with michael spencer about his convergence branch 17:24 yes.. I think pure qml apps will escape mostly unscathed 17:25 balloons: true, since they are quite dependant primarily on the SDK 17:25 unless they expose a bug in uitk or u1db or platform... 17:25 yep, exactly 17:26 ok. anything else nik90 ? 17:26 I'll cancel next weeks meeting 17:26 nothing else 17:26 awesome. Thanks nik90 17:26 #action nik90 Get keyboards shortcuts branch in by this week 17:26 * meetingology nik90 Get keyboards shortcuts branch in by this week 17:27 nik90: lemme know if you need any more branches reviewing or testing 17:27 popey: will do 17:27 thanks. 17:27 the big one is the alarms branch atm 17:27 yeah 17:27 ok, it's a wrap! 17:27 #endmeeting