Couldn't you have a policy that every patch is reviewed first by someone who wants to be an expert in that area, and then by someone who is currently an expert. Then you have the best of both worlds. The patch is reviewed by someone will make sure it won't cause problems, and the want to be expert gets training and will eventually be able to be the expert.
On Nov 11, 2009, at 12:58 PM, Josh Berkus wrote: > >> True, but even I avoid patches I don't understand, and "practicing" by >> applying them could lead to a very undesirable outcome, e.g. >> instability. > > Right, but being responsible for applying the patch is the only real > incentive anyone has to learn enough to understand its effects. If a > contributor is not responsible, they can always think "oh, Tom will get > it, I'll learn that later." > > --Josh Berkus > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
