On Tue, Jun 25, 2013 at 11:06 AM, Noah Misch <n...@leadboat.com> wrote: > On Mon, Jun 24, 2013 at 10:10:11AM -0700, Josh Berkus wrote: >> On 06/24/2013 10:02 AM, Dimitri Fontaine wrote: >> > Josh Berkus <j...@agliodbs.com> writes: >> >> patch. The vast majority chose not to respond to my email to them at >> >> all. When private email fails, the next step is public email. >> > >> > The only problem I have here is that I don't remember about deciding to >> > publish a list of failures by public email at all. I hope it's not my >> > memory failing me here, because then I would have to remember why I >> > didn't speak up against that idea at the time. >> >> You didn't decide anything. As the CFM, I did. My job for this month >> is to make sure that 100% of patches in that queue get reviewed and >> either committed or bounced by July 15th. I'm doing my job. > > +1 for trying the management practices you're trying. After the CF is closed, > we can step back and treat ourselves to a nice debate about them. Same here. +1. This method is good to gather in a single, short email all the information a common user cannot see by watching the commitfest page, becoming hard to understand globally with a growing number of pending patches. -- Michael
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
