I don't think it is that arbitrary. Certain packages are more critical than others.
Some are near the root, others are near the leaves. Dependencies make a difference. There are times when cooker branches are reaching for functionality, other times stability. Some efforts head down a dead end path or at least one that will have to be reversed. Knowing the topology of the dependency maps, the frequencies of bug submissions, posting of positive test results could steer development and testing in a positive way. Aggregates such as KDE3 could be uploaded in batches. There are times when the tasks to be done are known. Jim Tarvid On Wednesday 29 May 2002 04:57 pm, you wrote: > Le Mercredi 29 Mai 2002 21:31, Robert Fox a �crit : > > All I mean is - there are some periods when Cooker is fully non-usable > > (when it's in transition) and other times when it can be installed - > > > > It would be nice to know when Cooker (as a whole) is broke or when it > > can at least be installed and tested. > > Yep, there could be some kind of totally arbitrary measurement for the > cooker heartbeat, starting at OOW (Out Of the Womb), mounting to ICBW (It > Can't Be Worse) and then descending toward NC (Near Completion) and > Completed status. > > At the present time, I should say we are not yet at the ICBW state, but > fast as it goes, we could reach it in a matter of ... (OH, OH, CONNECTION > LOST). > > CU > CPHIL
