On Wed, Nov 11, 2009 at 5:06 PM, Jaime Casanova <jcasa...@systemguards.com.ec> wrote: > On Wed, Nov 11, 2009 at 4:40 PM, Robert Haas <robertmh...@gmail.com> wrote: >> On Wed, Nov 11, 2009 at 4:21 PM, Jaime Casanova >> <jcasa...@systemguards.com.ec> wrote: >>> why we need a full time manager at all? >>> why not simply use -rrreviewers to track the status of a patch? of >>> course, we hope the author or reviewer to change the status as >>> appropiate but we have seen many people including missing discussions >>> and changing the status of hanging patches... >> >> Well, actually, that's precisely were I've been putting in a ton of >> work - making sure patches aren't left hanging. > > that's why i guess sending automatic mails would be a good way to > remember that a reviewer had a patch in their control or to tell > reviewers/committers there are still patches for review/commit
I think an automatic system would probably not be too valuable, but you're welcome to submit a patch against commitfest.postgresql.org (source code is published at git.postgresql.org). I'd recommend proposing a design on -hackers first. It's easy to generate systems that spew out a lot of email, but the system doesn't really have any understanding of what is really going on. When I send out emails to nag people, I actually put quite a bit of thought into what I say. Sometimes I try to summarize the current status of the patch, sometimes I add my own thoughts, sometimes I just fire off a one-liner. I think that adds value, but perhaps I overestimate myself. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers