Difference between revisions of "Submission Policy"

From Rosalab Wiki
Jump to: navigation, search
(fix markup)
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]]".
 +
*'''List of project and corresponding git branches:'''
 +
{| class="wikitable"
 +
|-
 +
! Project
 +
! Package Suffix
 +
! Corresponding git branch
 +
|-
 +
| ROSA 2012 Marathon
 +
| rosa.lts2012.0
 +
| rosa2012lts
 +
|-
 +
| ROSA 2012.1 Devel
 +
| rosa.2012.1
 +
| rosa2012.1
 +
|}
  
 
[[Category:Packaging Policies]]
 
[[Category:Packaging Policies]]

Revision as of 18:13, 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.

An example of correct branch/repository settings
  1. 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. See the picture for an example.
  2. Always raise the release of the package you built, or changes in the package will not be added to the metadata.
  3. All packages built for a repository must be build from the corresponding branch
Caution!
Dialog-warning.png
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".

  • List of project and corresponding git branches:
Project Package Suffix Corresponding git branch
ROSA 2012 Marathon rosa.lts2012.0 rosa2012lts
ROSA 2012.1 Devel rosa.2012.1 rosa2012.1