Ben Reser <[EMAIL PROTECTED]> writes:
> to chase the maintainer to bother to apply. The TMOUT bug in the setup > package (in fact in this case it was Warly). Despite the fix being well > known and included in the 8.2 errata, having an updated setup package in > 8.2's updates it took probably 5 or 6 emails and finally getting > downright nasty before Warly bothered to even reply. Let alone applying > the patch. [...] Despite having spent a day figuring out the problem and > numerous emails reminding Warly to fix the package, I still didn't get > credit. This is my only and unexcusable fault, I know that it takes forever for me to fix this stupid thing, for various reasons. And you are right I forget to add a credit, I will add it next time I build a setup. > Truth is Mandrake's developers do not follow well known and established > best practices of the development industry. I am not sure that there are a lof of companies developing a 4000 components OS with a release time of 6 months with a better bug fixing than us. This does not mean our is perfect, it is far from it, but we couldn't apply old methods, we need to find new ones I think. [...] > If people want that to change then perhaps we should boycott submitting > bug reports on the list until Mandrake's developers take bugzilla or > some other bug reporting system (anthill perhaps) seriously. I'm up for > it. I'll just put up a page on my site with fixed packages and bug > reports. Make Mandrake work harder to get things fixed. But I'm > unlikely to do this on my own. We are not against you, and we understand how frustrating it is not to be listened, and we are opened to suggestions to improve the process. -- Warly
