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)!

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:Train: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.

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.

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.

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.

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:Zed: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:Ussuri: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:Victoria: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:Wallaby: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:Xena: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:Yoga: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:Zed:Staging!

Configuration and customization of cloud instance

Configuration and customization of cloud instance

The updates here are generated via a daily Github Workflow from https://github.com/openSUSE/autoupdate-perl .
To generate the spec https://github.com/openSUSE/cpanspec is used.

Then someone has to manually go over the updates and create submit reqests to devel:languages:perl (currently usually done by @tinita).
That last step is currently not automated because too many modules need manual handling (fixing license, dependencies, description etc.)

If you see a failing module, you can branch it from here and try to fix it.

Passenger is an Apache module for Ruby on Rails support.

Authors:
--------
Phusion - http://www.phusion.nl/

Rack provides a minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call.

Rack provides a minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web servers, web frameworks, and software in between (the so-called middleware) into a single method call.