Difference between revisions of "Submission Policy"
From Rosalab Wiki
Pavel.shved (Talk | contribs) (fix markup) |
|||
| Line 1: | Line 1: | ||
Here is a short list of rules that maintainers must follow when submitting builds of their ABF projects to official [[Repo Policy|ROSA repositories]]. | Here is a short list of rules that maintainers must follow when submitting builds of their ABF projects to official [[Repo Policy|ROSA repositories]]. | ||
| − | + | [[File:Sendtobuild.png|thumb|An example of correct branch/repository settings]] | |
| − | + | ||
| + | # 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. 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. | # 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 |
{{warning|failing to follow these rules may—and will—result in having your fixes '''automatically''' discarded from the repositories!}} | {{warning|failing to follow these rules may—and will—result in having your fixes '''automatically''' discarded from the repositories!}} | ||
Revision as of 15:54, 21 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. 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".
