Thanks Jarno. Very appreciate your solving qa-reports performance issue which ever made us headache pretty much.
Rgds jwang From: Jarno Keskikangas [mailto:[email protected]] Sent: Wednesday, June 22, 2011 6:51 PM To: Timo Härkönen Cc: Wang, Jing J; [email protected] Subject: Re: [Meego-qa] qa report tool development plan and deployment? On 22 June 2011 12:24, Timo Härkönen <[email protected]<mailto:[email protected]>> wrote: Hi On Wed, 2011-06-22 at 11:46 +0300, Wang, Jing J wrote: > I notice qa-report tool at > https://meego.gitorious.org/meego-quality-assurance/qa-reports is in > active development, and there are commits every day. I have several > questions > > 1) If current developments are all based on meego.com<http://meego.com> > bugzilla? > > 2) What's other development plan except to existing FEA list in > bugzilla? Our current focus is on QA Dashboard<http://wiki.meego.com/Quality/QA-tools/QADashboard> deployment and Crash Reports<http://wiki.meego.com/Quality/QA-tools/CrashReports> prototype development, so there's no major new features planned for QA Reports at the moment. In QA Reports, we are focusing on performance improvements and cleaning up some parts of the code base. Additionally, we're conducting user interviews, which might introduce new feature requests as we finish the interviews and analyze the results. All the things coming to Meego QA Reports should be in MeeGo bugzilla. Currently all the feature requests should be in bugzilla. Refactoring tasks have been usually just on our physical taskboard, as they shouldn't introduce visible changes to the user. As there are now more QA Reports installations running and more contributors working on the project, I totally understand it might also be valuable to see the refactoring tickets. Let's discuss this in the IRC. > 3) Deployment/Update for http://qa-reports.meego.com is still > weekly based currently, right? It is better send a notification to > mailing list, let us know what changed. > Would be nice. We are deploying QA Reports master branch usually on daily basis to qa-reports.meego.com<http://qa-reports.meego.com>. Announcements are sent on the list in case there's significant new functionality or changes in the current functionality. We could improve our practices on this and send announcements on smaller enhancements too. > 4) How about Open the account registration for > http://qa-reports.meego.com? > > At least I prefer to have to access process as it is. All the users have all the rights there and by requesting access through bugzilla is a good sanity check. Agree on this with Timo. In the long run, the plan is to integrate QA Reports with meego.com<http://meego.com> accounts. However, don't hold your breath on it. We are currently integrating QA Dashboard with meego.com<http://meego.com> accounts and honestly, it's been a painful navigation through the enterprisy policies. Nevertheless, all the credit for MeeGo IT supporting us, they've been extremely helpful. > > Hope we can sit together to discuss qa-report tool development and > deployment in next week's QA tool IRC meeting. Sure =) In case you have something specific on your mind, feel free to start the discussion, for example at #meego-qa. Yeah. haven't seen the guys in the meetings lately. But they are pretty much every day in #meego-qa if want to chat with the QA reports devs We'll, we've been present at least yesterday and last week. =) However, we're usually just following the discussion in case the topics are not related to reporting. Br, Jarno
_______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
