Hi,
I just read the "Why ?" thread.
I suspect that the "because" is due to a couple of factors :
1.Time preasure - RedHat has released something, and Mdk is a rival, so
it needs to follow.
2.Other events happening - there was some conference before the release or
something, and the right people weren't always available, so some
assumptions had to be made, and unfortunatelly some of these assumptions
turned out to be wrong.
3.The requests for enhancements that people had posted weren't properly
recorded and recognized by the people that assign to the Mdk developers
tasks. I expect that Mdk didn't want to be lousy on the visual
presentation, but due to confusion and overwhelming number of other
issues, these did get overlooked.
Not much can be done about 1., but 2. & 3. could potentially be
eliminated if cooker testers (list readers and posters), were able to put
their findings and even suggested fixes (patches) into an online bug
tracking database. Then Mdk wouldn't hopefully release a distro if they
saw that a problem serious enough exists. And I'm sure, being under the
time pressure, they would welcome if people suggested some patches in the
online bug tracking db that they could utilize.
Is Mdk already using a bug tracking db internally ? Would it be possible
that cooker audience could browse it and submit new bugs / finding / fixes
/ patches ?
TTYL,
Jan
--
-- Gospel of Jesus is the saving power of God for all who believe --
## To some, nothing is impossible. ##
http://Honza.Vicherek.com/
