Keith Lofstrom said:
I got some feedback, so I will go on to prescription. A
"conservative",
one-piece-at-a-time development process is of course much too slow.
Instead, I would divide up the work into domains so that people can
choose a domain and test in that. Where to draw the line is difficult,
but I would probably make the domains "kernel and drivers", "installation
and update", "X and desktops", and "applications". Obviously,
many
problems will cross domains, but to the extent that you can partition
things you reduce the scope of most problems.
What is preventing you from updating the "domain" you choose from Rawhide
and testing?
--
William Hooper