Hi,
ext Dave Neary wrote:
Eero Tamminen wrote:
Nokia is currently the one with most MTF applications & testing which
provides the fast feedback loop on issues that applications developers
are encountering when using it.
I.e. I think in this MTF "maturization" period there's some benefit
of this tighter coupling.
The problem is that the longer this coupling continues, the harder it is
to change. The more bugs that are open against MTF with potentially
sensitive information, the more work there is to open development
afterwards. The longer developers continue to follow internal processes
and not have to think about community developers, the harder it is for
them to change their work habits.
I think this would produce better bug reports for the MTF. Application
developers would need to write test-cases that are specific to MTF
instead of re-assigning to MTF bugs that are filed against their
(closed) apps and which test-cases are specific to those apps, not MTF.
Nokia has experience with this from the past, and I would have thought
the opportunity for a "do-over" with MeeGo would have meant not making
the same mistakes again in the interests of short-term expediency.
If MTF would be at some point merged with Qt, the bug tracker
wouldn't be bugs.meego.com though, then it would be at qt.nokia.com.
I.e. MTF bugs being public might (time wise) depend also on this
kind of decision.
Do you have an escalation route for driving this issue?
Who's responsible for MeeGo bugs & QA in general?
- Eero
(This kind of a error reporting transition would take long,
so better start it early. It's not my worry though, somebody
else with some free time needs to drive it...)
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
