Difference between revisions of "Submission Policy"
From Rosalab Wiki
Pavel.shved (Talk | contribs) |
|||
| Line 3: | Line 3: | ||
[[File:Sendtobuild.png|thumb|An example of correct branch/repository settings]] | [[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. | + | # 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. | # 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 | ||
| Line 10: | Line 10: | ||
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" | {| class="wikitable" | ||
| − | |||
! Project | ! Project | ||
! Package Suffix | ! Package Suffix | ||
| − | ! | + | ! Git Branch |
|- | |- | ||
| ROSA 2012 Marathon | | ROSA 2012 Marathon | ||
Revision as of 19:32, 13 June 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 2012 Marathon | rosa.lts2012.0 | rosa2012lts |
| ROSA 2012.1 Devel | rosa.2012.1 | rosa2012.1 |
