On 10/7/10 11:09 PM, "[email protected]" <[email protected]> wrote:
> Hi Rolla, > >> I accepted, but question (and forgive me if this is common >> knowledge)... >> >> Where are the test results posted? (was it the just in the email >> entitled "Testing old LMT with new mcompositor" or something official from >> QA?) > > Inline on BMC#7881, far from official testing by QA. > >> What HW do you test on? > > N900 > >> The Compositor effects many different verticals, and I want to make >> sure testing is done on a few different platforms, and not just one... > > We are aware of the risk and moving to MeeGo 1.1 testing is only a step. > It has been decided to do more testing (official from QA on the different > verticals) > as soon as this package is available in MeeGo 1.1 testing. > The final decision is still not done and Sean Kelley is responsible > to follow this bug (and influence the final decision). Ok...in general, MeeGo:1.1:Core:Testing _is_ considered more of a final step than a stepping stone...the idea is that for important pkgs (like qt-mtf related ones), QA do due diligence on all effected verticals, not just n900, before submitting to :Testing. I understand this is a very dire situation, so I'm letting you know for the future... Where are the QA results from MeeGo:1.1:Core:Testing posted? Specifically the ones that test the QT-MTF functionality? rs > > That's my understanding. > > Cheers, > > Fathi > > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
