m (Fix repository list) |
(Add link to packaging guidelines.) |
||
| Line 30: | Line 30: | ||
TBD: A set of rules for promotion to Extras. These rules will need to be tested by the community and some automated tests would need to be done too. | TBD: A set of rules for promotion to Extras. These rules will need to be tested by the community and some automated tests would need to be done too. | ||
| + | |||
| + | == Packaging == | ||
| + | |||
| + | Any package in the Extras repositories must follow the [[Packaging/Guidelines]]. A package will be checked against these guidelines before promotion to Extras-testing. | ||
Contents |
[WIP]
MeeGo Extras is the repository where software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sofisticated build system. These applications can be published into the end-user facing Extras repository after certain conditions have been met.
A developer will need to request access to the Community OBS (procedure TBD). 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 Extras 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 Extras-testing. The promotion request triggers some automated tests on the package (TBD). The Extras-testing repository is intended for stability testing and community QA. If the package meets all promotion criteria, it will be moved to the Extras 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:
TBD: A set of rules for promotion to Extras-testing. The rules need to be tested automatically.
TBD: A set of rules for promotion to Extras. These rules will need to be tested by the community and some automated tests would need to be done too.
Any package in the Extras repositories must follow the Packaging/Guidelines. A package will be checked against these guidelines before promotion to Extras-testing.