> Ok, OK
> <snide-remarks>
> Lets stop the presses...
>
> All of those CD's that were made in the manufacturing plant must be thrown
> out, so that we can update a package that may, or may not ever be used by
the
> average person.
> </snide-remarks>
>
> SOLUTION: How about everyone here compromises a little bit?
>
> tomsrtbt advocates:
>
> stop flaming mandrake for something they can no longer change. GET OVER IT
IT
<SNIP>
>
> Mandrake People:
>
> lets issue an errata on the day of release of 7.1: in the updates system
for
<SNIP>
>
> This *should* placate everyone here, and lower the signal/noise ratio of
this
> list
>

Rhetoric aside, there were other issues involved that had not been shared
with the beta testers; there is a great deal of inside discussion that does
not make it to the public list.

For example,

The MUO newsletter mentioned a "rumored" June 1st release which appeared to
be officially discounted on this list, but was awfully close to the truth.
It seems likely that the date had actually been set for some time. The
commitment by Mandrake for the release date likely had to do with agreements
made to third parties (MacMillan?) or they would have mentioned this facts
here. They may even be working on "punching a ticket" in preparation for an
IPO and can't discuss it - but none of the beta testers really know for
certain what was going on. A classic communication problem.

There do,  however,  appear to be unresolved bugs and issues (tomsrtbt the
least significant issue - and thanks, Tom for a great effort to release the
very useful new version) that seem to have been addressed simply by Mandrake
pronouncing the release candidate "final" while not having made the repaired
files available to the beta testers. The beta testers are understandably
concerned, as should Mandrake be.

An honest look at this entire process exposes the growing pains of the
Mandrake distro and MandrakeSoft. Certainly there are things we all can do
together to make it a better process and produce a better product. Perhaps
this is what should be addressed first rather than (or at least parallel
with) candidates for a new feature set. I don't know that the disrto could
use another bug in 7.1 like the first 7.0 had (That DrakX/FAT resize
disaster? The press let Mandrake off easy on that one).

Everyone take a deep breath. It has been a stressful beta period for all
involved. Let's wait for the mirrors to fill up and enjoy this for now - we
can get back to work tomorrow.

Hoyt


Reply via email to