Robert Schweikert - 14:18 12.12.13 wrote:
... @ ALL TECHNICAL CONTRIBUTORS/DEVELOPERS (sorry for shouting) - If we collectively manage to "calm" factory down to the point where it will always boot and you do not have to fiddle with the very low level, kernel, bootloader, glibc , X11, things after doing "zypper dup" would you be
- inclined - very likely - unlikely - very unlikely
to switch to factory on your every day working machine?
Those that run factory already should probably not answer this question ;)
Well, I run factory on my less used desktop and I run it on my notebook since some beta or something when it should be calm enough. If we stabilize it, I'll run it on my notebook all the time and I'll migrate my server to Factory :-)
... One of my primary concerns that has not really received an answer, I think, is of the number of people that now get the "promotion" to staging tree manager.
- do we have people that work at the level of code that requires staging trees willing to take on the "new", additional work/responsibility?
Well, people have to do it nowadays anyway, they just break Factory and have to fix it in Factory while Factory is broken while now the breakage will move into staging tree and get merged once it's fixed.
- are we introducing a new set of arbitrary decision points?
Kinda. Currently reviewers have rpmlint and several bots to help them with review, in the new workflow, they will two additional optional "helpers" - staging projects and some basic QA.
- do we need to think of trying to develop/find a number of people that are interested in being primarily staging tree chaperones?
I do not believe that we should have special role/people for staging tree management. It should be managed by whoever is the maintainer of the package that this project was created for. This person have the most knowledge to see/decide whether he has a bug in his package, or other people depending on him. But there will be definitely some notification actions needed in OBS to help the manager...
So we want to have a distributed, balanced and robust development process ie share the workload among teams with different roles. To make sure we get motivated people for those teams the process needs to be set up in a way that promotes mentoring and recognition➄.
Well, yes. But I'd say of all things we probably struggle with the recognition part the most, from my perspective at least.
Well, there is this Karma thing to do the recognition...
... Will a more everyday usable factory automatically lead to a reduced effort of testing in the end game?
I believe yes. Not only testing, but also integration. Nowadays coolo has to hunt everybody down to fix their stuff so he can release a milestone. Getting milestone to compile and produce DVD is actually a lot of work. And if that would be done in Factory during development continuously... -- Michal HRUSECKY SUSE LINUX, s.r.o. openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org