openSUSE:Backports Package Submission Process

Jump to: navigation, search

Overview

In general, the submissions process of SUSE Package Hub is identical to that of openSUSE Leap.

Package Hub 16.0

Submissions to Package Hub 16.0 are accomplished via a pull request targeting the "leap-16.0" branch of the package's pool git repo at 

   https://src.opensuse.org

For example, if you want to change the source code of package "hello", you would fork 

   https://src.opensuse.org/pool/hello

For details, see the Leap 16.0 submission guidelines here: 

   https://en.opensuse.org/openSUSE:Packaging_for_Leap

Project Setup for Package Hub 15

Package Hub 15 is a rebuild of all openSUSE Leap 15 packages that are not also in SLE or are otherwise excluded from being added to Package Hub 15. As a consequence, Package Hub 15 automatically receives maintenance update changes from Leap 15.0 that the openSUSE community delivers for these packages, with the help of SUSE employees.

The following projects are active:

Packager workflow for Package Hub 15

By default, all changes delivered to Leap 15 will be reflected in Package Hub 15 for applicable packages. Any other changes and new packages may be submitted in parallel to the following projects:

  • openSUSE:Backports:SLE-15-SP6:Update
  • openSUSE:Backports:SLE-15-SP7:Update

As a consequence, new packages and changes have the following requirements:

  • A bug entry in bugzilla, referenced in the submission
  • New packages accepted in openSUSE:Factory
  • Bug fixes first submitted to openSUSE:Factory
  • Compatible with the base Leap and it's maintenance policy.

Maintenance Workflow

The target projects do not actually build the packages but behaves like an update project for released openSUSE distributions. I.e. the actual sources are built in so called "incident projects". The openSUSE maintenance team takes care of those incident projects.

After the packager filed a request, they reviewed by automated review bots:

  • maintbot: checks if the submission was created by the package maintainer as defined in the devel project. maintbot will add the devel project as reviewer for submissions by non-maintainers.
  • factory-source: checks if the sources for submissions to the Backports project are actually accepted in factory. Rejects requests where this is not the case.
  • legal-auto: license checks

The following further reviews are added as needed:

  • for Backports team: If the sources do not match those of openSUSE:Factory or a currently maintained stable Leap distribution, this deviation must be separately approved
  • for the Factory package maintainers. If the submission is by a person who is not in the list of regular maintainers of this package in Factory, they need to separately approve it. Note that if the maintainer accepts this reviews, this also indicates that they commit to maintain the package in Package Hub for future security or maintenance issues. The following message is used: Submission for PACKAGE by someone who is not maintainer in the devel project (PROJECT). Please review.

After successful automated and manual reviews the maintenance engineer takes over. If the request is ok he accepts it and therefore creates a maintenance incident. After the packages built successfully the maintenance engineer creates a release request. The release request in turn is checked again by factory-source.

After the usual grace period for testing as used on openSUSE the maintenance engineer then accepts release requests to actually release the package.

Introducing a single new package

New packages must be submitted from a branch. The branch can be created like so: 

 osc branch -M -N openSUSE:Backports:SLE-15-SP6:Update <pkg>

Package Hub 12

NOTE: Package Hub 12 is EOL. Submissions are no longer possible.

Retrieved from "https://en.opensuse.org/index.php?title=openSUSE:Backports_Package_Submission_Process&oldid=198633"