On Fri, May 27, 2011 at 2:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Fri, May 27, 2011 at 12:21 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> That patch is waiting for a committer who knows something about Windows
>>> to pick it up.
>
>> It might be useful, in this situation, for the OP to add this patch to
>> the CommitFest application.
>
>> https://commitfest.postgresql.org/action/commitfest_view/open
>
>> Also, I think it's about time we got ourselves some kind of bug
>> tracker.
>
> [ shrug... ] I think the main problem is a lack of committer cycles.
> If so, the extra bureaucracy involved in managing a bug tracker will
> make things worse, not better.
>
> However, if someone *else* wants to do the work of entering bugs into a
> tracker and updating their status, far be it from me to stand in their
> way.
Definitely something to think about. But I think lack of committer
bandwidth is only part of the problem. If someone had a free day
tomorrow and wanted to flip through all the bugs that haven't had a
response and address the ones they knew something about, how would
they get a list?
And who is to say only committers can fix bugs? Actually commit the
fixes themselves, yes. Write the patches? No.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
