libpurple crashing since 18 months

[Felipe Contreras]

On Thu, Mar 26, 2009 at 5:05 AM, Ka-Hing Cheung <khc at hxbc.us> wrote:
> On Wed, 2009-03-25 at 16:51 +0100, Thorsten wrote:
>> I am not going to file a bug report, because what you are doing is
>> mainly managing bug reports instead of fixing bugs. I know what I am
>> talking about, I operate my own professional software development
>> business and bugs are fixed through direct communication, not by
>> managing them on web pages (at least if no one cares or only cares "a
>> little" after weeks have passed).
>
> I know what I am talking about, I am a professional software developer
> and bugs are fixed through bug tracker, not by direct communication
> (because no one will remember whether an issue is fixed after the 1200th
> email). Surely direct communication may work if you are the center of
> the universe though.

What about projects that solve bugs on the mailing list? Surely the
bugs must be forgotten and the result is low quality software... like
the linux kernel
http://marc.info/?t=123733287400005&r=1&w=2

For a quick list of critical bugs that were not fixed, just closed
automatically after 2 weeks of not providing some information:
http://developer.pidgin.im/ticket/8637
http://developer.pidgin.im/ticket/8561
http://developer.pidgin.im/ticket/8544
http://developer.pidgin.im/ticket/8534
http://developer.pidgin.im/ticket/8055
http://developer.pidgin.im/ticket/7873
http://developer.pidgin.im/ticket/7809
http://developer.pidgin.im/ticket/7795

This one is priceless: "For future reference, we do not accept bug
reports against monotone code unless they are accompanied by a patch
to fix the problem."
http://developer.pidgin.im/ticket/8278

The code on the master branch on your SCM should always be stable, and
bug reports on top of that should be even more appreciated because it
allows to fix things *before* the issue hits a release. Not to mention
that bugs filed against the latest release might already been fixed on
the head of mtn.

-- 
Felipe Contreras