El 30/07/13 13:08, Robert Schweikert escribió:
The idea is that we define components, this is going to be a chunk of work, and for each component we define it's dependencies.
Dependencies change all the time, how you will define "dependencies" in a sustainable manner that does not require eternal tweaking ? his component then gets released every time a
new kernel is released and every time a new gcc or glibc are released, or based on some other criteria the core team determines and publishes.
The kernel is a component completely unrelated to GCC or glibc for the matter. and all of those move a quite different paces.
Lots of work, yes, but in the long run we have to make some changes. Thus, the sooner we start the easier it will be.
Sounds like an even more complicated approach that will cause eternal paralysis of analysis and won't get anything done, at least not done at a pace compatible with the proposed schedules. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org