Development process issues
Posted May 2, 2011 18:37 UTC (Mon) by tchernobog
Parent article: New features in PostgreSQL 9.1
The biggest problem the project struggles with is the constant torrent of patches and feature ideas being submitted, which has been growing at a much faster rate than the pool of reviewers and committers has.
I know they are really used to it, but having a public bug-tracker would make development *much* easier in my opinion. Handling bugs in mailing lists always looked like a... er... "strange" idea to me. Dependencies, severity and history tracking, not to mention things like automatic commit monitoring and closing of bugs (for example, Redmine does it) are things that are not easy to do with plain-text e-mails. Also, everyone subscribed to MLs receive the whole corpus of all bugs, and searching for dupes is fairly harder.
to post comments)