Hi I've been thinking about this a bit and we have a couple of options how to do this. Currently test packages seem only to live in different people's obs home projects which of course is not the way to do it.
So here's my take on how they could be handled: 1) Push all the test packages into Trunk via Trunk:Testing just like everything else going into MeeGo. 2) Create a new project (e.g. Tests:Testing) for core and other tests that are run regularly in automated testing - packages that are not tied to specific versions of components in MeeGo. Having them in some other project would make them faster to deploy and easy to add on top of any image just by adding that repo. Tests that are written for applications, libraries, etc. would still go the trunk path since they are tied to that specific version and need to be in the same place as the software that they are written for. personally I'd prefer option 2 but in any case we need have test packages somewhere else than in people home projects - hopefully sooner than later. Thoughts? BR -Timo _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
