openSUSE Package Sources

This organisation is the common source for all openSUSE and SUSE products.

Sources in official branches have successful passed the review.

Create pull requests against the right branch to request changes. Please find details to the workflow here: https://src.opensuse.org/openSUSE/git-workflow-documentation

A branch may not exist, if the package source is not used in that code stream.

Official branches:

Branch	Description	Pull Requests	OBS Reference Build Project
factory	Package sources of openSUSE Tumbleweed aka Factory	not yet	openSUSE:Factory
			openSUSE:Factory:ARM
			openSUSE:Factory:LegacyX86
			openSUSE:Factory:PowerPC
			openSUSE:Factory:RISCV
			openSUSE:Factory:zSystems
leap-16.1	openSUSE Leap 16.1 and PackageHUB	yes	openSUSE:Backports:SLE-16.1
Leap-16.1	temporary special branch for openSUSE Leap 16.1 overlayd packages	yes	openSUSE:Leap:16.1
leap-16.0	openSUSE Leap 16.0 and PackageHUB	yes	openSUSE:Backports:SLE-16.0
Leap-16.0	temporary special branch for openSUSE Leap 16.0 overlayd packages	yes	openSUSE:Leap:16.0
slfo-main	Next generation SLES code base	no	SUSE:SLFO:Main
slfo-1.2	SLES 16.0 and openSUSE Leap 16.0 base packages	no	SUSE:SLFO:1.2

These projects are also managed via git repositories. The package sources are managed via submodules for the code streams. This is usually only important for code stream maintainers themself. You can find these code streams git repositories here:

openSUSE specific code streams are defined in https://src.opensuse.org/openSUSE
common SUSE and openSUSE code streams are defined in https://src.opensuse.org/products

Maintainership

The maintainership is defined per package, branch and code stream. However, the most important one is the openSUSE Factory one. Given that Factory is not yet moved to git native it is still not filled yet.

For openSUSE Leap, including PackageHub, the information can get found here:

The workflow-pr bot assigns reviewers based on this information to pull requests.