17:11 <mhall119> #startmeeting Calculator App 17:11 <meetingology> Meeting started Thu May 23 17:11:07 2013 UTC. The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:11 <meetingology> 17:11 <meetingology> 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:11 <mhall119> Launchpad: https://launchpad.net/ubuntu-calculator-app 17:11 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calculator-development 17:11 <mhall119> Burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-calculator-dev.html 17:11 <mhall119> so the burndown chart looks good 17:12 <mhall119> several things are blocked, but that looks to be all visual design stuff 17:12 <boiko> yes 17:12 <mhall119> and things are assigned to the month-2 milestone already 17:12 <mhall119> you guys are on the ball 17:12 <mhall119> :) 17:12 <boiko> so, calc devs are running out of tasks 17:13 <mhall119> balloons: want to talk about autopilot? 17:13 <boiko> autopilot tests are broken, discovered yesterday 17:13 <balloons> mhall119, basically my same speech :-) 17:13 <balloons> specifically yes, ap tests for calc are broken 17:13 <balloons> however I understand some work to fix them and port them to 1.3 was done 17:14 <boiko> isn't autopilot tests being run for MRs in the calc-app branch? 17:14 <mhall119> not yet, not by jenkins 17:14 <daliusd> Hi 17:15 <mhall119> hey daliusd 17:15 <balloons> boiko, no not yet. Martin is still working on getting a jenkins up to do this, but it's been hindered by a few things 17:16 <boiko> balloons: ok 17:16 <balloons> one way to help is to get the calc's autopilot tests running properly 17:16 <boiko> yes, that for sure helps 17:16 <balloons> ideally he'd like a test that is working to test the enviroment out 17:16 <boiko> balloons: I can try to fix the tests today, but I am actually loaded with other prioriaty tasks :/ 17:17 <boiko> daliusd: I talked to omer, the tests were already broken, another change that went in must have broken it 17:17 <balloons> boiko, no worries.. Just put it on the schedule to get looked at. I believe someone from the ap team did some work on the tests 17:17 <boiko> balloons: yes, omer ported to ap1.3 17:17 <daliusd> boiko, maybe, but based on python errors it is somewhere in autopilot 17:17 <daliusd> because it finds buttons "1" "2" "3" 17:18 <boiko> daliusd: indeed 17:18 <daliusd> and the same function fails with button "=" 17:18 <daliusd> and there is nothing in test code what would make it fail 17:18 <boiko> daliusd: in any case, I will try to look at it later today 17:19 <daliusd> at least that's my impression looking at autopilot's test first time (and at python code not first time) 17:19 <daliusd> OK 17:21 <mhall119> thanks boiko 17:22 <mhall119> so, besides visual design, is there anything you guys are blocked on? 17:23 <daliusd> No 17:23 <daliusd> Everything is fine 17:23 <daliusd> There are two defects for you mhall119 :) 17:23 <mhall119> cool 17:23 <daliusd> Could you check them 17:23 <daliusd> maybe I could do something 17:23 <mhall119> so, I'm defining milestones for Alpha, Beta and Final releases of each of the core apps 17:23 <daliusd> It would be nice to close all the defects 17:24 <mhall119> daliusd: what are the defects? 17:24 <daliusd> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1153787 17:24 <daliusd> https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1170096 17:24 <daliusd> Maybe they are simply not closeed 17:25 <mhall119> daliusd: I'll double-check them and close them if appropriate 17:25 <daliusd> Thanks :) 17:25 <mhall119> so like I said, I'm defining alpha, beta and final release milestones for all core apps 17:26 <daliusd> One defect is for Riccardo 17:26 <mhall119> clearly calculator has passed alpha level already 17:26 <daliusd> and another needs design input - I will try to get it tomorrow in design meeting 17:26 <daliusd> Cool :) 17:26 <mhall119> do you feel that it's passed beta level already too, or do you think we should mark June as our beta? 17:26 <daliusd> What are beta requirements? 17:27 <daliusd> Or you are my opinion? 17:27 <daliusd> are -> ask 17:27 <mhall119> asking opinion 17:27 <boiko> mhall119: I think for beta we need at least the final visual design in place 17:27 <mhall119> since you've already gotten all the functional requirements done 17:27 <daliusd> I agree with boiko 17:27 <daliusd> beta is something that we can give for beta testers/users 17:28 <daliusd> and difference between beta and release are minor fixes 17:28 <mhall119> ok, so I'll put Beta for month-3, which will be mid-July, and matches several of the other core apps 17:29 <mhall119> and then final for month-4, mid-August 17:29 <mhall119> which will give enough time for it to be in the phablet image 1.0 release 17:30 <boiko> looks good 17:30 <daliusd> I will have vacations in the end of summer so I hope we will get design before that :) 17:30 <boiko> daliusd: good point 17:31 <mhall119> I do too 17:33 <mhall119> alright, thanks guys, you're doing a great job running this project 17:33 <mhall119> especially keeping on top of the Blueprint and work items 17:33 <mhall119> #endmeeting