On Fri, Oct 9, 2020 at 12:50:36PM -0400, Tom Lane wrote: > Magnus Hagander <mag...@hagander.net> writes: > > That said, having this in a different format would in no way fix the fact > > that the information is mislabeled and obsolete. It would likely be > > equally mislabeled and obsolete in an issue tracker. Just look at almost > > any of the other projects out there that *do* use an issue tracker and have > > been around for 20+ years. > > The long and the short of it is that a list like this is only of value > if it gets diligently maintained. Putting the data in a different tool > changes nothing about that. (A tool might reduce the effort involved, > *if* it's a good match to your workflow. But it won't reduce the effort > to zero.) > > Consulting the wiki page's edit history shows that Bruce has been > doing some maintenance work, but almost nobody else does. Evidently > that's not enough. > > I'd be +1 for the "aggressive culling" suggested upthread, but > I'm not particularly volunteering to do it, either.
+1 -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
