Home Wiki > openSUSE:Leap development process
Sign up | Login

openSUSE:Leap development process

tagline: From openSUSE

About Leap - Report Bugs - Contribute to Leap - Leap development process

This article will give you a view from of the development lifecycle and concepts of openSUSE Leap. It is provided to explain the different steps of creating Leap on the base of SLE and how a release is put together.

Concepts and steps of the development process of openSUSE Leap

  • all maintenance updates for Leap version-1 are automatically pushed (over the full cycle until the version gets frozen)
  • all SLE12SPx updates are automatically pushed (over the full cycle)
  • all packages which came from Factory originally should be submitted again by a maintainer if an update is desired for the next Leap version. The target audience for Leap and a seamless upgrade process has to be kept in mind. To support this and to make sure there are no things forgotten, during the lifecycle a tool will check all packages with Factory origin for successful build status against the developed Leap and will perform submissions which can be accepted by the maintainer easily. Non-accepted requests will not be included.
  • over the full time active submissions from Factory to Leap will be considered for acceptance if the package builds and was not coming from SLE12 before. Submissions need to be either performed by the maintainer or if not, the maintainer has to approve the update.
  • in case a package should be switched from SLE12 to Factory or vice versa a review process will be triggered for leap-reviewers group
  • packages which were forked from SLE12 _and_ Factory because of certain reasons must be reviewed if they can possibly be upstreamed back to SLE12 of Factory
  • new packages in SLE12 or Factory should be reviewed for inclusion into Leap; automatic tool submissions will/might be performed

OBS tools to manage some of the above steps can be found here: https://github.com/openSUSE/osc-plugin-factory