From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: The purpose of the core team |
Date: | 2015-06-11 18:50:38 |
Message-ID: | 5579D87E.9010704@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/11/2015 11:47 AM, Alvaro Herrera wrote:
> After going over this a few times, there is one thing that strikes me
> that nobody has mentioned: the list of tasks mentioned there has one
> that's completely unlike the others. These are related to human
> relations:
>
> Acting as a conduit for confidential communication.
> Making policy announcements.
> Managing permissions for commits, infrastructure, etc.
> Handling disciplinary issues.
> Making difficult decisions when consensus is lacking.
>
> while this one is highly technical:
> Coordinating release activities.
>
> It seems that only this last one is where most people seem to have a
> problem. I wonder if it makes sense to create a separate group that
> handles release activites -- the "release team."
De-facto, this is Packagers. Which is maybe not the best system, but
it's what we're doing now.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2015-06-11 18:56:11 | Re: 9.5 release notes |
Previous Message | Robert Haas | 2015-06-11 18:50:27 | Re: Cancel race condition |