Robert,
thanks for pushing this forward. It's been discussed on last year's(!)
openSUSE conference without any follow up.
* Robert Schweikert
Behind the "smooth sailing" appearance is a ton of work that is ever increasing and getting ever more complex. The current push model leads to problems we experience every time a new gcc version shows up, a bunch of stuff breaks and only 2 or 3 people fix things.
That's the core of the problem IMHO, factory development needs to scale better. The load to keep factory building/working must be shared by more shoulders. Sharing the load is a matter of a) responsibility and b) availability of information. About responsibility: Having your package / component in factory means you are responsible for it. If a maintainer can't accept this responsibility, then why does he want his package in Factory ? A package in Factory must build, be installable, and working. Availability of information directly relates to that: - build If some change in Factory breaks the build, I want to see it in _my_ (devel) project. This is information is not _easily_ available to me currently. And, no, I don't want to spend like 5 to 10 minutes waiting for the Factory 'Status' page to build up and then have to search for my packages. - installable There should be an automated way to check if a package is installable. Could be an image build or openQA. - working openQA seems to be the right approach. Every package in Factory should have a testcase and be covered by openQA. Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org