also since mandrake 5.3 I've been on this list you should see some of
the things that go on back here between beta test cycles. Some times the
system won't boot whatever. You can even tell when a beta test is going
to start happening because the install works pretty good and the system
is fairly stable with a fair amount of new packages. At about that time
it will be beta in about a week.

Also mandrake this is for you guys. Thanks for not moving cooker to a
new directory this time for beta testing as I usually don't take part in
the beta cycle for this reason. I like all this stuff in one place.

Anyway most of the bugs are actually worked out between beta testing
cycles by the time beta hits everything isn't to bad. Which is why the
beta testing goes so fast. 

I don't really know what the infatuation is with iso's as since the
beginning I have mirrored the directories and installed from my hard
drive. All that want to help in this should try the same if they need to
be completely up to date. Most sites I imagine would not even want to
carry the iso because of the server load. Trust me I started out doing
this on a 56k modem and it is allot easier to update 50 or 60 megs than
650 or 900 as the case is now. 


Mandrake thanks for the distro. I like the development process and enjoy
testing it. 

Ron Stodden wrote:
> 
> Chmouel Boudjnah wrote:
> 
> > Sorry Ron, our development process is a OpenSource development in
> > the Bazaar style where everything is published the soon as we code it.
> 
> Hardly!   Where is the testing required to ensure the coder's
> confidence in his work?
> 
> And, after that, where is the testing to ensure that the coder's
> module works properly in conjuction with all the other developers'
> modules?   Testing up to completion of this is called Alpha testing.
> 
> Your remark makes properly organised Beta testing all the more
> imperative, not less.
> 
> --
> 
> Regards,
> 
> Ron. [AU] - sent by Mandrake Linux.

Reply via email to