On 26 September 2014 08:48, Heikki Linnakangas <hlinnakan...@vmware.com> wrote:
> But in many cases, lack of good documentation makes even reviewing the patch > difficult. How do you determine if the patch works as intended, if you don't > know what it's supposed to do? Exactly. Lack of review and lack of consensus are often caused by the author not making the patch fully and genuinely accessible to peer review. Don't say you're having problems getting buy in when you've done very little to encourage that. Committing early is not the solution. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
