| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Chris Browne <cbbrowne(at)acm(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Feature Freeze date for 8.4 |
| Date: | 2007-10-23 21:39:43 |
| Message-ID: | 20071023213943.GH2333@fetter.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-23 21:50:39 | Re: Feature Freeze date for 8.4 |
| Previous Message | Chris Browne | 2007-10-23 20:59:51 | Re: Feature Freeze date for 8.4 |