At 16:22 01/11/2003 +0100, Ulf Erikson wrote:
>* Andrew I. Mutch [2003-10-28 06:00]:
>> Go ahead
>> and triage the list to "has to be fixed" for 0.8 and what can wait.
>> asmpgmr has already started that list.
> I find it okay to wait with old bugs.
Bugs should be corrected as soon as possible. Delaying them more, because
they are already old, is a bad excuse. ;)
Note that it's the kind of practice we don't like to see from M$.
> If the same problem was around in
> K-Meleon 0.7/0.7.1 and no one pushed for having it fixed earlier it
> cannot have been such a big issue that we need to block a release due
> to it.
As long as work to correct the bugs is continued after the release, it's
OK. But don't wait another year, and yet again use the same excuse. ;)
I find it useful to have the pressure of a release force correction of
bugs. Else, when would they be corrected?
>> Forum Bugs:
>> * Resource Leak in bookmarks:
> Nothing has changed since km07/071.
Yep. That's exactly the problem, it hasn't been fixed in a year.
> If it was a major leak it would have been reported more frequently.
Because having KM vampirise all available resources after only opening 9-10
windows/popup/layer, is not a major leak ?
A reason for not reporting the bug is that not many users have a resources
meter running. When the program crashes, or behaves badly, they can't
connect the problem to the leak. Even less to which plugin is at fault.
Note that KM is not a major browser. Mozilla usage is already limited to a
niche marked, KM is even less used. Don't expect many people accurately
reporting bugs. You'll have even less computer savvy users able to locate
the exact source of the problem, and willing to report it.
Up until a week ago I though KM was a dead project. At the beginning of
this year a search on google still returned the dead link
Worse, I usually search directly on freshmeat or sourceforge to find
open-source projects. KM page on sourceforge,
<http://sourceforge.net/projects/kmeleon/>, doesn't even have a link to the
correct homepage of the project (http://kmeleon.sourceforge.net/). The only
reason I've found the page is that I knew there was a 0.7.1 patch, and it
wasn't available in the downloads.
Users can easily dismiss KM when only reading this page.
And the last nail... :o)
They don't bother to report bugs, because they already have a working free
browser, IE, and don't want to debug programs (and stop using them).