Wolfgang Rosenauer wrote:
Am 13.12.2016 um 14:03 schrieb Ludwig Nussel:
So for the Leap 42 line that means 42.3 based on SLE12 SP3. In anticipation of that OBS already has openSUSE:Leap:42.3 set up as copy of 42.2. It already accepts submissions. Right now mostly to directly integrate 42.2 maintenance updates.
it feels like I'm asking similar questions with every Leap release but somehow as it's only done once a year so I tend to forget ;-)
That's fine, hits me too :-) Some things change over time so it never hurts to ask.
I found https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but I miss a bit more information there how the development cycle of a Leap version works. E.g. a list like: - all maintenance updates for Leap version-1 are automatically pushed (over the full cycle)
Yes. Until 42.3 itself gets frozen and flagged as maintained distribution.
- all SLE12SPx updates are automatically pushed (over the full cycle)
Yes.
- all packages which came from Factory originally and build against the new Leap project will get updates to current Factory versions
Packages that were already in 42.1 or 42.2 and came from Factory there are not automatically updated. Ie 42.3 started with a mapping that specifies that all packages track maintenance updates from 42.2 resp SLE. Package maintainers have to manually submit an update from Factory to flip the origin to the Factory version.
submitted for review to the packager; only actively accepted reviews will be submitted to Leap
Yes. In general submit requests to leap have to be approved by the package maintainer(s). Package maintainer information is taken from Factory.
- over the full time active submissions from Factory to Leap will be accepted if the package builds and was not coming from SLE12 before; in case a package should be switched from SLE12 to Factory there should be a review process and an argument about that fact
Yes. A bot keeps a watch on attempts to change the origin of packages. The "leap-reviewers" group gets added as reviewer to approve such requests.
- packages which were forked from SLE12 _and_ Factory because of certain reasons should be reviewed if they can possibly be upstreamed back to SLE12 of Factory
Yes.
- new packages in SLE12 or Factory should be reviewed for inclusion into Leap
Yes. Right now new packages are not automatically submitted to 42.3. For Factory we used to do this in batch rounds later in the development process. I'm not sure if there's any reason that would prevent us from doing that right away though.
Please note that the above are just the points which came to my mind. They are not ordered nor complete and probably not even how it works actually. That's why I would like to have such a list consolidated into a wiki page so developers/packagers have a better idea what happens by the process or what needs manual actions. I also think that people have written small tools to create lists and submissions. It would be very nice if we could collect them also in a list so they can be reused easily.
The scripts and bots I know of are maintained in https://github.com/openSUSE/osc-plugin-factory
Therefore please give some feedback if something like the above already exists or if it would be useful if it doesn't.
It is useful. Feel free to extend the cited wiki page with information you miss. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org