Hello, Time to get the ball rolling on getting test packages to MeeGo. Timo Härkönen suggested (http://lists.meego.com/pipermail/meego-qa/2010-December/000652.html) putting the packages under Tools:Testing and as no one came up with better idea or objections to that I created Tools:Testing:Tests subproject.
So how this will work from now on (similar to getting stuff to Trunk:Testing http://wiki.meego.com/MeeGo_Release_Creation#How_the_code_reaches_the_Trunk.2FRelease) : 1) Follow the MeeGo packaging policy http://wiki.meego.com/Build_Infrastructure/Packagers_Developers#MeeGo_Packaging_guidelines_and_Howto and work with the package in your home project 2) Make sure it works in devel: project. If your team does not have devel: project request one through bugzilla (Meego Community Infrastructure/Build Service/Build Service) or requests access to devel:quality:tests from me. 3) submitrequest to Tools:Testing:Tests from the devel: project (not from home:) and have a reference to a bugs.meego.com id in .changes and in your submitrequest comment. 4) if rejected - fix it and resubmit More info about OBS: http://wiki.meego.com/Build_Infrastructure First packages are now in devel:quality:tests and hopefully soon in Tools:Testing:Tests. If you have questions please ask here. -Joonas _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
