Difference between revisions of "Submission Policy"

From Rosalab Wiki
Jump to: navigation, search
(changed naming as per TC meeting on 22 Aug)
 
(One intermediate revision by the same user not shown)
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]]".
*'''List of project and corresponding git branches:'''
+
 
 +
=== Product Naming ===
 
{| class="wikitable"
 
{| class="wikitable"
|-
 
 
! Project
 
! Project
 
! Package Suffix
 
! Package Suffix
! Corresponding git branch
+
! Git Branch
 
|-
 
|-
| ROSA 2012 Marathon
+
| ROSA Marathon 2012
 
| rosa.lts2012.0
 
| rosa.lts2012.0
 
| rosa2012lts
 
| rosa2012lts
 
|-
 
|-
| ROSA 2012.1 Devel
+
| ROSA Desktop 2012
 
| rosa.2012.1
 
| rosa.2012.1
 
| rosa2012.1
 
| rosa2012.1

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.

An example of correct branch/repository settings
  1. 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 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".

Product Naming

Project Package Suffix Git Branch
ROSA Marathon 2012 rosa.lts2012.0 rosa2012lts
ROSA Desktop 2012 rosa.2012.1 rosa2012.1