Difference between revisions of "Submission Policy"

Revision as of 15:07, 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 rosa2012lts branch.

Here is the example of correct settings for sending package to be built:

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".

@@ 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]].
-# 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.
+Here is the example of correct settings for sending package to be built: [[File:Sendtobuild.png|thumb|center]]
 # 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