[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#321102: please don't



Riku Voipio wrote:
> On Thu, Apr 13, 2006 at 07:53:14PM +0200, Bastian Venthur wrote:
>> No, please! Don't close the bug "just in case it has been fixed".
>> Upstream confirmed the bug, marked them as hard to reproduce and
> 
> That's not the point. It's just a "heads-up" for you - Can you or can 
> you not reproduce the bug with latest version?

Nope, I can't -- mainly because I don't want to lose anymore mails. I
switched to Thunderbird after an "accident" two months ago. But at least
one of the upstream developers confirmed the bug mentioned a problem
with KDE's IMAP KIO-slave. Since he has not fixed (or closed) the bug
yet, I assume it's still open.

As a programmer, I don't believe in bugs fixing them self "somehow" just
because the version number has increased. If someone had worked on the
bug and found a fix, he surely would have left at least a note on the
bugreport, wouldn't he?

The bug is confirmed, marked as "critical" by upstream and still open
why should we assume it is closed?


>> A better solution would be to increase the pressure on upstream to fix
>> this bug. 
> 
> Increasing pressure doesn't really work on volunteers.. They are just 
> likely to find more interesting tasks to work on. More debugging info,
> instructions for easier reproducing etc work better.

Please note, I don't wanted so sound rude, but someone came up with the
following idea:

Quoted from the upstream bugreport [1]:

"FYI, since upgrading to KDE 3.5.2 (Debian), my KMail IMAP problems and
crashes have gone away.  If you have had this problem, please test with
3.5.2.  If we don't get any more reports in, say, a couple of weeks, I
think we should consider closing this bug."

and I just wanted to make sure this bug does not get closed too
frivolous. I was using KMail for *months* without problems, until
suddenly the bug hit me again -- so closing the bug if no one confirms
within a couple of weeks sounds pretty irresponsible for me.


Kind regards,

Bastian

1. http://bugs.kde.org/show_bug.cgi?id=104956#c54




Reply to: