| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Commitfest infrastructure (was Re: 8.4 release planning) |
| Date: | 2009-01-27 18:58:33 |
| Message-ID: | 20718.1233082713@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Tom,
>> Oh. What's that "watch this page" option do, then?
> Notifies you when anyone makes any change of any kind to *any* patch (or
> piece of text, for that matter) in the commitfest. Including something
> like changing the number of patches assigned to an RRR.
Okay, so it does have notification ability and you do want that, you
just want it on a different granularity level.
> My inability to systematically send reminder e-mails to submitters and
> reviewers -- or for that matter, even track when they were assigned or
> last updated -- has been a significant drag on the effectiveness of the
> commitfests. Some patches stalled, and I missed them.
Agreed, that would be helpful, and the wiki doesn't help you with it.
So we want a patch tracker that can do that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2009-01-27 19:04:25 | Re: pg_upgrade project status |
| Previous Message | Joshua Brindle | 2009-01-27 18:57:26 | Re: 8.4 release planning |