Re: The purpose of the core team

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: 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-11 15:26:49
Message-ID: CA+TgmoY17-9gYDiLqusdZUuJ6PY37ELz8KQPo3ok6BaNp2vaeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 11, 2015 at 11:13 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Yes, and we have recently been discussing how best to solicit those
> opinions this year.

Great!

>> As a non-core team member, I find it quite frustrating that getting a
>> release triggered requires emailing a closed mailing list.
>
> It does not, unless you're talking about a security release. You might
> have to prod people if they overlook an email on -hackers, but you can
> certainly suggest releasing updates there.

I certainly can suggest it in a variety of ways on a variety of
mailing lists. Getting it to happen is a different thing.

> Timing *decisions* are not made by -core, as I've told you in the
> past. They are made by the packagers who do the actual work, based on
> suggestions from -core.

You have told me that in the past, and I do not accept that it is true.

The suggestions from -core are always accepted, or as near as makes no
difference. So in effect, -core decides.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-06-11 15:32:37 Re: 9.5 release notes
Previous Message Simon Riggs 2015-06-11 15:17:55 Re: Entities created in one query not available in another in extended protocol