| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: The purpose of the core team |
| Date: | 2015-06-12 15:56:54 |
| Message-ID: | CA+TgmoYbkfr1U8qb=_8kThJynzoZSm4Q8oat30ma-1S2G6skdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 12, 2015 at 1:21 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Deciding "WHAT goes in the next release?" is what Committers do, by
> definition.
>
> It seems strange to have a different mailing list for "WHEN is the next
> release needed?", so those two things should be combined.
Core team members have sometimes taken the position that this is
already so; that releases should be discussed on pgsql-hackers and
pgsql-security as appropriate to the driver. In theory, this may be
fine, but in practice, it doesn't seem to be working very well right
now.
> Packagers should be about "HOW do we make the next release", which is
> separate from the above.
>
> Ultimately, "How" effects "When", but "When is it needed?" is an earlier
> thought.
+1. Completely agreed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-06-12 16:29:03 | Re: Further issues with jsonb semantics, documentation |
| Previous Message | Tom Lane | 2015-06-12 14:33:10 | Re: git push hook to check for outdated timestamps |