Difference between revisions of "Submission Policy"
From Rosalab Wiki
Pavel.shved (Talk | contribs) (add categ) |
Pavel.shved (Talk | contribs) (changed naming as per TC meeting on 22 Aug) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| 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]]. | ||
| − | # 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 | + | [[File:Sendtobuild.png|thumb|An example of correct branch/repository settings]] |
| − | # | + | |
| + | # 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 <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. | ||
| + | # 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!}} | ||
If a repository is frozen, the updates should be submitted as described in "[[Requesting an Update]]". | If a repository is frozen, the updates should be submitted as described in "[[Requesting an Update]]". | ||
| + | |||
| + | === Product Naming === | ||
| + | {| class="wikitable" | ||
| + | ! Project | ||
| + | ! Package Suffix | ||
| + | ! Git Branch | ||
| + | |- | ||
| + | | ROSA Marathon 2012 | ||
| + | | rosa.lts2012.0 | ||
| + | | rosa2012lts | ||
| + | |- | ||
| + | | ROSA Desktop 2012 | ||
| + | | rosa.2012.1 | ||
| + | | rosa2012.1 | ||
| + | |} | ||
[[Category:Packaging Policies]] | [[Category:Packaging Policies]] | ||
Latest revision as of 19:45, 22 August 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. 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 |
