On Thu, Sep 3, 2009 at 11:55 AM, Joshua D. Drake<j...@commandprompt.com> wrote: > On Thu, 2009-09-03 at 11:41 -0400, Robert Haas wrote: >> On Thu, Sep 3, 2009 at 11:38 AM, Joshua D. Drake<j...@commandprompt.com> >> wrote: >> > On Thu, 2009-09-03 at 07:44 +0300, Peter Eisentraut wrote: >> >> On ons, 2009-09-02 at 12:52 -0700, Joshua D. Drake wrote: >> >> > Isn't "core" supposed to be the release manager? >> >> >> >> The core team has historically been the release *maker* and has some >> >> done management of the final phases of that process. But I think the >> >> sentiment is growing that we need more management throughout the entire >> >> release cycle. >> > >> > O.k. so a "release" team. Cool. I am assuming the team would be more >> > directed toward upcoming major release versus minor releases to past >> > revisions. We already pretty much have that under control between -core >> > and -packagers. Yes? >> >> +1. > > O.k. so the second part of this, is I feel it should contain a majority > of people who are not already being slammed into the ground by community > work. E.g; let's get some fresh blood. It is certainly important to have > a couple of long standing contributors involved but we have some people > that have cropped up recently (relatively) within our community that > could probably be overworked a bit more ;) > > Joshua D. Drake > > /me pokes Robert Haas and Kevin Grittner
Yeah, I'm game, though I'm hoping not to become the guy who spends all his time doing release planning, because I like writing code, too. Hopefully Selena won't mind my mentioning that she sent me a private email expressing some interest in this area, too. And /me pokes Brendan Jurd. :-) ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
