On Sun, May 01, 2016 at 01:00:22PM +0200, cagsm wrote:
Hi there,
I am trying to understand how quickly and via which steps and workflow the updates to packages of a default opensuse distro are being released, and who decided where and when and how (transparently) and where discussions of the updates take place and so forth.
I have for example found: https://build.opensuse.org/project/maintenance_incidents/openSUSE:Maintenanc...
and the testing update repo for leap 42.1 for example and the default public update repo for leap 42.1
http://download.opensuse.org/update/leap/42.1-test/ http://download.opensuse.org/update/leap/42.1/
Do all those packages from the build Maintenance page first go into the test update repo? Where are they being discussed, results, breakage, satisfaction, respins, etc?
When do they move over to the public update repo if at all, or do they get re-built for the public repo?
Who decides all these steps and allows the workflow to continue?
I notice for example the Firefox 46 updates are still not published by opensuse although many other distributions have long ago on day 0 concurrently with mozilla source code and binary releases of ffx 46 released their patches and updated distro packages as well (e.g. debian).
I would like to understand how all this works and who decides on speed of releases, and on importance and impact and for delays and so on.
https://en.opensuse.org/Portal:Maintenance documents the basic maintenance workflow. I also talked about this on the Prague openSUSE conference. There are intermediate staging "incident" projects used, which are aggreated into the -test repositories. On release the exact binary packages are copied into the update repository. We usually do a 7 day hold on test updates to wait for feedback, be it positive or negative. On important updates we short cut this turnaround time, but do some own testing. For some weeks we also use openQA for testing Leap 42.1 updates as automated process. There is not much discussion happening, usually updates just go through the process silently. The coordinators are the openSUSE Maintenance Team and/or the SUSE Security Team, these are the decision makers and takers. Delays happen for submission, the QA Hold, and if there are build troubles. The current Firefox update is staged in openSUSE:Maintenance:5017, and would be ready for release, excepting the QA hold time or some independed testing. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org