I've said this before... but I'll say it again... Rushing a release to meet a schedule, instead of releasing when fully stable, ends up hurting the distro in the long run. With Redhat, Sun, Lindows, Xandros and a host of others now focusing on the desktop (of which Mandrake has been the leader until now) means that extra scrutiny will be placed on this release. If things don't work out of the box, many people will wipe it and try Redhat, etc. The tolerance for outstanding bugs will be much lower for a while. Since Mandrake plans on this being the last of the 6 month release schedule, I think getting it just right before release becomes even more important.
Ben Reser ([EMAIL PROTECTED]) wrote*: > >On Sat, Sep 21, 2002 at 02:04:51PM -0400, Felix Miata wrote: >> I had thought the original target was the 15th, but regardless, my >> report was approximately 31 hours after rc2 iso's were on the mirrors. I >> think that's a respectable interval to get the iso's downloaded, install >> the distro, discover the problem, search for prior similar reports, and >> finally report the problem. > >Maybe if it was new bug in RC2. But you said in your initial bug >report that it was observed in the earlier betas. Report bugs when you >find them not at the last minute. If you see it in a beta report it in >a beta. Waiting till an RC is up is a guaranteed way to ensure that >there won't be enough time to meet the schedule and resolve your issue. > > >Never take no as an answer from someone who isn't authorized to say yes. > -- SI Reasoning [EMAIL PROTECTED] gpg public key ftp://ftp.p-p-i.com/pub/si-mindspring-pubkey.asc The significant problems we face cannot be solved by the same level of thinking that created them. -Albert Einstein
