Bruce Momjian wrote: > This is an interesting observation that deserves to be discussed > separately, and relates to the patch queue. Many people want to know > what is happening with the patch queue but having better reporting > doesn't seem to help much the people who are actually processing the > queue, and requires more work.
I'm not sure I follow. I tried last week to give some hours for patch review. What actually happened was that I had to wade through a ton of stuff, skipping patches that were already applied, threads that were purely discussion but not patches, threads about earlier versions of some patches. I did manage to find actual patches, but I had then to resort to my own mailbox to get the actual patch to apply and review. Now I can't be sure whether the current commitfest is finished or there are still patches pending review; what patches could use input from me; what patches I could bounce to the next commitfest. Also I don't know what patches we have for the next commitfest. I would gladly give some time to put up a Wiki page to list the patches for the next commitfest. Would that be helpful? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. - Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
