Staging projects are for automated package builds of their respective stable release (i.e OpenStack Juno). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branche
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Juno)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Liberty:Staging!

A massively scalable cloud operating system. Contains always the latest upstream OpenStack code.

OpenStack project: https://www.openstack.org

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Mitaka:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Mitaka). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Mitaka)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Newton:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Newton). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Newton)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Ocata:Staging!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Pike:Staging!

The project is derived from Cloud:OpenStack:Pike:cisco-apic to build these packages for OpenStack Newton on SLE 12 SP3 to be used with SUSE OpenStack Cloud 8. The usage of this project with SOC8 requires the APIC firmware to be upgraded to version 2.3 or higher.

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Pike). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Pike)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Queens:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Queens). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Queens)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Rocky:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Rocky). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Rocky)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Stein:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Stein). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Stein)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

DON'T SUBMIT HERE DIRECTLY, USE Cloud:OpenStack:Train:Staging!

Staging projects are for automated package builds of their respective stable release (i.e OpenStack Train). New packages come from either:

- The trackupstream Jenkins Job, following the upstream commits in the stable branches
- Packagers, doing security / bug fixes

Each package submission triggers a testsuite run. Once that passed, the package submission should be safe to go to the stable branch. This means that direct package submissions to stable projects are a taboo (i.e. no submissions to Cloud:OpenStack:Train)!

If you add this repository to your openSUSE installation, make sure it has a higher repository priority in zypper. Otherwise you will end up using the wrong dependencies depending on your openSUSE release.

Submit requests to this project will be ignored. Instead, please submit a
gerrit review to https://opendev.org/openstack/rpm-packaging