Hi List, I was delighted to be informed by the good Maemo bug master that that this bug [0] has been resolved with the last PR1.3 update, released today.
My question to QA people and teams (it has been a while since I was involved with QA in meego so please bare with me) - What sort of infrastructure do we have in place to make absolutely sure this will not regress in further versions of MeeGo, if hypothetically this bug had been originated in MeeGo ? If not I think we should start spec'ing and designing it ASAP, or is the BOSS wrapper around OBS for continues integration solves that as well? And on a related note, besides the dear bug master's talk, are there any other people interested in discussing quality that might be good to pre-announce so people can plan ahead and decide to which talks BOFs they want to attend? [0]: https://bugs.maemo.org/show_bug.cgi?id=8747 Cheers, -Sivan _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
