> > The plea is always please test, give us the means to test and we
> > will.
>
> Well, i think that people forget that mandrake employees are working.
> They do not break mirrors for pleasure, and they are fully aware of the
> problem.
>
> Do you really think they try to slow down the test ? to annoy their
> testers ?
>
> no, they are working on it, and all we have to do is to wait. Sometimes,
> a solution is not easy to find, or take time to be applied.

It's a question of priorities. The *very first* priority for Mandrake should 
be to have a reliable distribution system so that testers and users can 
supply timely and pertinent bug reports and feedback. When someone submits a 
bug report they have the reasonable (but mistaken) belief that because they 
have the latest rpms (they don't much of the time) their report is relevant 
to the current state of the Cooker.

Furthermore, a common situation is for a new package to be released which 
fixes problems that people may be continuing to have because their mirrors 
are not up-to-date. They put up with those problems (if they can't fix them) 
and submit bug reports. A waste of time and effort. If their mirror had been 
up to date, they might not be experiencing those particular issues and could 
be concentrating on _things_at_hand_.

I know the developers do a great job. All I am suggesting is that they 
prioritize this issue so people can stop wasting bandwidth (which is money), 
time (which is also money), and effort (which is a very finite resource!).

Cheers,
Paul.


Reply via email to