Re: Feature Freeze date for 8.4

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: David Fetter <david(at)fetter(dot)org>
Cc: Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature Freeze date for 8.4
Date: 2007-10-23 22:19:42
Message-ID: 471E737E.8090607@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter wrote:
> On Tue, Oct 23, 2007 at 04:59:51PM -0400, Chris Browne wrote:
>
>> tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:
>>
>>> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
>>>
>>>> I'd suggest we have multiple checkpoints during the cycle.
>>>> Checkpoint is a "patch queue blitz" where we stop developing and
>>>> reduce the queue to nothing. Perhaps a two-week period where
>>>> everybody helps reduce the queue, not just Tom and Bruce. Every
>>>> outstanding patch gets told what they need to do in order to get
>>>> it committed. FF is then just the last in a series of
>>>> checkpoints. Suggest we do a checkpoint every 2 months.
>>>>
>>> I like this idea ...
>>>
>> Don't we need to have a background writer process to gradually flush
>> this data so that checkpoints aren't so massive? ;-)
>>
>
> I'm proposing a DSCM with easy branching and merging to implement this
> background writer process :)
>
> The one below is already available, so we don't have to do a "flag
> day" with it.
>
> http://repo.or.cz/w/PostgreSQL.git
>
> There are git-cvsimport and git-cvsexport utilities which make
> communication between the legacy SCM and the DSCM straight-forward.
>
>
>

You are way ahead of us here. And my vote *still* goes to Mercurial, if
we're picking SCMs.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2007-10-23 22:23:19 Re: Feature Freeze date for 8.4
Previous Message Andrew Dunstan 2007-10-23 22:17:51 Re: Feature Freeze date for 8.4