m (moved MeeGo Extras to MeeGo Apps: Name defined) |
(now MeeGo Apps) |
||
| Line 1: | Line 1: | ||
| - | = MeeGo | + | = MeeGo Apps = |
[WIP] | [WIP] | ||
| - | MeeGo | + | 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. |
== Process == | == Process == | ||
| - | A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|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 | + | A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|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 | + | 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. |
== Repositories == | == Repositories == | ||
| Line 15: | Line 15: | ||
There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example: | There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example: | ||
| - | *'''MeeGo:1.1: | + | *'''MeeGo:1.1:Apps''' This targets MeeGo 1.1 Core. This means that applications in this repository can only have dependencies on MeeGo 1.1 Core and the repository itself. |
| - | *'''MeeGo:1.1: | + | *'''MeeGo:1.1:Apps:Handset''' This targets MeeGo 1.1 Core and MeeGo 1.1 Handset UX. |
| - | *'''MeeGo:1.1: | + | *'''MeeGo:1.1:Apps:IVI''' This targets MeeGo 1.1 Core and MeeGo 1.1 IVI UX. |
| - | *'''MeeGo:1.1: | + | *'''MeeGo:1.1:Apps:Netbook''' This targets MeeGo 1.1 Core and MeeGo 1.1 Netbook UX. |
*'''MeeGo:1.1:Surrounds''' This repository hosts libraries which are not included in MeeGo, but are a dependency for common Linux applications. | *'''MeeGo:1.1:Surrounds''' This repository hosts libraries which are not included in MeeGo, but are a dependency for common Linux applications. | ||
| Line 29: | Line 29: | ||
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. | 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 === |
==== Automated tests ==== | ==== Automated tests ==== | ||
* Does package name already exist in repository | * Does package name already exist in repository | ||
** If yes: Check if owner | ** If yes: Check if owner | ||
* Are all dependencies available in the repository or it's parents. | * Are all dependencies available in the repository or it's parents. | ||
| - | * Does it build against | + | * Does it build against Apps-testing |
* Does the package have a description | * Does the package have a description | ||
| - | === | + | === Apps === |
==== Automated tests ==== | ==== Automated tests ==== | ||
| - | + | Apps-testing tests plus: | |
| - | * Does it build against | + | * Does it build against Apps |
* Is it an application | * Is it an application | ||
** If yes: Is there at least one screenshot in the OBS package files | ** If yes: Is there at least one screenshot in the OBS package files | ||
| Line 54: | Line 54: | ||
== Packaging == | == Packaging == | ||
| - | Any package in the | + | Any package in the Apps repositories must follow the [[Packaging/Guidelines]]. A package will be checked against these guidelines before promotion to Apps-testing. |
Contents |
[WIP]
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.