Re: How long should it take to fix a obvious memory leak?
- From: Luis Menina <liberforce freeside fr>
- To: desktop-devel-list gnome org
- Subject: Re: How long should it take to fix a obvious memory leak?
- Date: Thu, 04 Apr 2013 18:55:48 +0200
Le 04/04/2013 18:30, Ma Xiaojun a écrit :
On Fri, Apr 5, 2013 at 12:26 AM, Luis Menina <liberforce freeside fr> wrote:
What kind of support do you expect from an unmaintained module ?
Then you just answer: "Probably forever."
I accept it.
pygtk stats:
https://bugzilla.gnome.org/browse.cgi?product=pygtk
148 bugs, 56 without response, 2 patches accepted but not committed (for
four years), 40 patches unreviewed...
From pygtk.org:
"Existing authors of PyGTK applications are also recommended to port
their applications to PyGObject to take advantage of new features
appearing in GTK-3 and beyond."
"PyGTK-2.24 will be the final major release of PyGTK. Additional bug-fix
releases may appear when necessary to maintain compatibility and
stability with the GTK-2.24 series."
Translate "may" here by "if someone steps up to do the work".
One fair argument is that it's a bit hard to know from the bugzilla
product page if maintainers have "resigned", but it just takes sending
an email to them to know that.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]