There is a sprint on this week (22/Apr->29/Apr) to integrate and deploy all the work done so far by various teams. This page will be the starting point for notes and docs. (Nb finishing this page isn't in the sprint!)
MeeGo Apps is the repository where software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met.
A developer will need to request access to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.
Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package (TBD). The Apps-testing repository is intended for stability testing and community QA. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.
There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example:
Following rules are proposed to be a starting point of QA and sanity checking. They are up for discussion and not final. These checks will be carried out before the package reaches the target repository.
Apps-testing tests plus:
Any package in the Apps repositories must follow the Packaging/Guidelines. A package will be checked against these guidelines before promotion to Apps-testing.