[opensuse-project] Some questions regarding Package Life-Cycle and other openFATE topics
Hi, Can somebody explain the package life-cycle. It will help me with openFATE screening. The are different repositories Nightly, Factory, obs, user repositories. So, how does the life-cycle of a package starts. The user uploads package at his obs page, it then submits to Nightly, then to Factory repo and maybe someday it will reach to the distribution repo. Is something missing in this process and how does this transfer takes place. The openFATE documentation regarding package wishlist needs to explain more than
A package wish is a wish for inclusion in the next openSUSE distribution release. The first step is to build the package in the openSUSE Build Service, the second step is to get it >into the factory distribution.
If a package is in factory repo or nightly repo should I make the feature package request as already completed or should make the status as marketplace or new. The the openFATE documentation explains about voting but the documentation for screening process doesn't anything about minimum requirement of votes to convert Unconfirmed feature to New. The documentation clearly explains if the description of feature is complete it can be set as new. But, where does voting come into place. Regards, Akash Vishwakarma (vish_99) -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On May 1, 2015 8:11:04 AM EDT, Akash Vishwakarma
Hi, Can somebody explain the package life-cycle. It will help me with openFATE screening.
The are different repositories Nightly, Factory, obs, user repositories. So, how does the life-cycle of a package starts. The user uploads package at his obs page, it then submits to Nightly, then to Factory repo and maybe someday it will reach to the distribution repo. Is something missing in this process and how does this transfer takes place.
For your task, you can ignore nightly and rings, etc. They are transition repos that only matter to developers. The highlights are: User manually creates a new package in home project. (Hopefully he tests it there first). Manual SR (submit request) to a devel (development) project. (Hopefully more testing in the devel project). Manual SR from devel project to factory. (Hopefully even more testing). When a new distro release is made, 100% of factory is branched to the new distro repo, so being in factory means a package will be part of the next distro release unless it gets removed from factory in the meantime. Note: direct SR from a home project to factory is not allowed. There has to be a devel project for every package in factory. fyi: There are more detailed steps in the SR to factory stage. This is where rings and nightly builds come into play, but that is just complexity you don't need to review openFATE entries. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (2)
-
Akash Vishwakarma -
Greg Freemyer