Re: feature freeze and beta schedule

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: feature freeze and beta schedule
Date: 2015-05-05 13:47:56
Message-ID: CA+Tgmob2h4_xRfbtuOjEYyQObetsUCqk=W2Lbnt86JmwnyzzmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 1, 2015 at 1:16 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> We really need to segregate the two.. By that what I mean is this: I
> want an "always-open" "bugfix" CF, which allows us to keep track of
> bugfix patches. Having something about "applies to versions X, Y, Z"
> would be nice too...
>
> /me prods Magnus

I don't really see that as a step forward. Right now there's one
place to look at for patches that somebody wants me (or someone) to
pay attention to, and, when time permits, I look at it. Dividing that
up into two places is not going to make me look at them more
frequently.

--
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 Magnus Hagander 2015-05-05 13:57:28 Re: feature freeze and beta schedule
Previous Message Robert Haas 2015-05-05 13:46:32 Re: pg_dump: CREATE TABLE + CREATE RULE vs. relreplident