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 <davidcous...@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@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
