[GNC-dev] What about outdated open bugs in Gnucash Bugzilla?

[Christian Gruber]

Ok, I'll start doing that on all bugs older than 10 years. If there is 
no reaction after at least one month, I'll close them as RESOLVED.

By the way, I found some bugs, which were already commented this way by 
"Wm", but without setting status to NEEDINFO. And he/she didn't close 
the bugs. I'll close these as well, if there is no reaction after at 
least one month. See https://bugs.gnucash.org/show_bug.cgi?id=459278 for 
instance.

Christian

Am 28.10.19 um 04:03 schrieb John Ralls:
> Colin,
>
> That's a worthwhile idea that could be easily applied to all bugs over n years old. One could start with n around 10, perhaps meaning everything against versions before 2.4.0.  Care to spend some quality time in Bugzilla?
>
> Regards,
> John Ralls
>
>> On Oct 27, 2019, at 3:14 PM, Colin Law <clanlaw at gmail.com> wrote:
>>
>> Possibly an alternative, used in Ubuntu for example, is when a version
>> goes out of support that any bugs against that version have a comment
>> added saying the version is out of support, saying that if the bug is
>> relevant to a later version then please to post a comment, and marking
>> the bug as needing info, so it will expire after a time if there is no
>> input,
>>
>> Colin
>>
>> On Sun, 27 Oct 2019 at 21:46, David Cousens <davidcousens at bigpond.com> wrote:
>>> John,
>>>
>>> Is there perhaps a need to place maintenance limits on GnuCash release
>>> versions,  i.e. at a specified time after release they become unsupported,
>>> as is bugs and all. This is more than likely what actually happens in
>>> practice given limited skilled developer time. As bug reports are often tied
>>> to a specific version, bugs could then be removed from bugzilla when the
>>> version they apply to becomes unsupported.  Most bugs are not show stoppers
>>> and those that are or are particularly inconvenient are usually fixed fairly
>>> quickly after release.
>>>
>>> Enhancement requests could possibly have a longer lifetime but perhaps there
>>> is a need for expiry on those as well. E.g. if they didn't make it into the
>>> next major release and you really need that feature you raise the issue
>>> again (or work on it yourself).
>>>
>>> David Cousens
>>>
>>>
>>>
>>> -----
>>> David Cousens
>>> --
>>> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html
>>> _______________________________________________
>>> gnucash-devel mailing list
>>> gnucash-devel at gnucash.org
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>> _______________________________________________
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel