[opensuse-factory] Workflow of updates being released
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:Maintenance> 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. TIA. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* cagsm <cumandgets0mem00f@gmail.com> [05-01-16 07:01]:
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 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.
As long as you have been here, have you not actually read any of the discussion here as it has been explained and explained .....? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
cagsm composed on 2016-05-01 13:00 (UTC+0200):
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).
FF45 is built with GTK2 toolkit, well supported by non-Gnome DEs. FF46 was switched to GTK3 toolkit, which will unlikely beneficial to any users of non-GTK3 desktops like KDE. The toolkit switch has caused several as yet unresolved UI problems for users of other DEs and even for Gnome users. See e.g. https://bugzilla.mozilla.org/buglist.cgi?list_id=12992990&short_desc=gtk3&re... which doesn't include a scroll behavior bug I've found that has not yet been reported as a separate issue AFAICT. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, May 1, 2016 at 1:17 PM, Felix Miata <mrmazda@earthlink.net> wrote:
FF45 is built with GTK2 toolkit, well supported by non-Gnome DEs. FF46 was switched to GTK3 toolkit, which will unlikely beneficial to any users of non-GTK3 desktops like KDE. The toolkit switch has caused several as yet unresolved UI problems for users of other DEs and even for Gnome users. See e.g. https://bugzilla.mozilla.org/buglist.cgi?list_id=12992990&short_desc=gtk3&re... which doesn't include a scroll behavior bug I've found that has not yet been reported as a separate issue AFAICT.
Yes thanks I read about that gtk stuff and Mozilla recently. But I am trying to understand the overall process of updates on opensuse, not just the Firefox delay. Firefox 46 and the decision to switch to gtk3 was probably long ago made, so all the distros not doing gtk3 would have known all along and need to make sure the gtk2 way to do Mozilla apps would be important. Anyways as I said I didnt figure out so far how all this goes or it is not yet familiar to me. The testing updates repo has the or some Firefox 46 packages already, I do wonder where these testing updates are being discussed? Do we have a list especially for that repo? TIA. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 2016-05-01 at 07:17 -0400, Felix Miata wrote:
FF45 is built with GTK2 toolkit, well supported by non-Gnome DEs. FF46 was switched to GTK3 toolkit, which will unlikely beneficial to any users of non-GTK3 desktops like KDE. The toolkit switch has caused several as yet unresolved UI problems for users of other DEs and even for Gnome users. See e.g. https://bugzilla.mozilla.org/buglist.cgi?list_id=12992990&short_desc= gtk3&resolution=---&classification=Client which doesn't include a scroll behavior bug I've found that has not yet been reported as a separate issue AFAICT.
Just to clarify, although upstream decided to ship gtk3 builds by default from mozilla.com, updated firefox 46 for Leap released through Maintenence will not be built against gtk3, but will continue to be based against gtk2 at least until most gtk3-only issues (like the one Felix reported here and there are several others [1]) have been resolved at the upstream level. Given that firefox is openSUSE's default browser, it makes sense for us to play it safe. An email regarding the roadmap to switching to gtk3 builds by default *for Tumbleweed only* was discussed in a mail sent to the -factory ML [2]. Whether you are on Leap or Tumbleweed, if you want to help test unofficial builds of firefox built against gtk3, please follow the discussion in [2], and please file bugs generously. Thank you very much. [1] https://bugzilla.mozilla.org/buglist.cgi?quicksearch=[GTK3]&list_id=12993532 [2] https://lists.opensuse.org/opensuse-factory/2016-04/msg00293.html
-- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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:Maintenance>
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
Hello, Thanks for the information. On Sun, May 1, 2016 at 1:47 PM, Marcus Meissner <meissner@suse.de> wrote:
https://en.opensuse.org/Portal:Maintenance documents the basic maintenance workflow. I also talked about this on the Prague openSUSE conference.
Are there a presentation or papers and or video available?
There are intermediate staging "incident" projects used, which are aggreated into the -test repositories. There is not much discussion happening, usually updates just go through the process silently.
Do interested peers subscribe to that testing update repo instead of the normal update repo or additionally and then install all the testing and report back here on factory ml or what would make sense? Or do we manually fetch the rpm files from the testing update repo and try them manually? Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Atri Bhattacharya -
cagsm -
Felix Miata -
Marcus Meissner -
Patrick Shanahan