Re: commit fests (was Re: primary key error message)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: commit fests (was Re: primary key error message)
Date: 2010-01-21 23:05:09
Message-ID: 4B58DDA5.8010209@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> But I don't think that should mean everyone has to drop everything when
> the clock strikes midnight and must now only look at things that the
> magic commitfest page has pre-approved.
>

Well, we used to have the idea of a feature freeze ... is that going to
apply at the end of the commitfest?

I generally agree that we need to have a bit of wiggle room at this
stage - small and non-controversial items can be allowed to creep in still.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joachim Wieland 2010-01-21 23:07:55 Re: Listen / Notify - what to do when the queue is full
Previous Message Peter Eisentraut 2010-01-21 22:35:14 commit fests (was Re: primary key error message)