Difference between revisions of "Submission Policy"
From Rosalab Wiki
Pavel.shved (Talk | contribs) (add categ) |
|||
| Line 2: | Line 2: | ||
# Each ABF project '''MUST''' have a branch corresponding to a target platform. For instance, a project that yields packages for ROSA 2012 Marathon '''MUST''' have <code>rosa2012lts</code> branch; | # Each ABF project '''MUST''' have a branch corresponding to a target platform. For instance, a project that yields packages for ROSA 2012 Marathon '''MUST''' have <code>rosa2012lts</code> branch; | ||
| + | # 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 [[Repo Policy|repository]] must be build from the corresponding branch | # all packages built for a [[Repo Policy|repository]] must be build from the corresponding branch | ||
Revision as of 14:14, 18 May 2012
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. For instance, a project that yields packages for ROSA 2012 Marathon MUST have
rosa2012ltsbranch; - 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".
