Submission Policy
From Rosalab Wiki
Revision as of 19:45, 22 August 2012 by Pavel.shved (Talk | contribs) (changed naming as per TC meeting on 22 Aug)
This is a page snapshot, showing old (but not deleted) versions of images and templates.
Here is a short list of rules that maintainers must follow when submitting builds of their ABF projects to official ROSA repositories.
- Each ABF project MUST have a branch corresponding to a target platform. See "Git Branch" column in #Product Naming section for the branch for each release series. For instance, a project that yields packages for ROSA 2012 Marathon MUST have
rosa2012ltsbranch. See the picture for an example. - Always raise the release of the package you built, or changes in the package will not be added to the metadata.
- All packages built for a repository must be build from the corresponding branch
Caution!
failing to follow these rules may—and will—result in having your fixes automatically discarded from the repositories!
If a repository is frozen, the updates should be submitted as described in "Requesting an Update".
Product Naming
| Project | Package Suffix | Git Branch |
|---|---|---|
| ROSA Marathon 2012 | rosa.lts2012.0 | rosa2012lts |
| ROSA Desktop 2012 | rosa.2012.1 | rosa2012.1 |
