From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com> |
Subject: | Re: First CommitFest: July 15th |
Date: | 2009-07-03 06:19:32 |
Message-ID: | 200907030919.35448.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday 03 July 2009 05:16:41 Robert Haas wrote:
> On Thu, Jul 2, 2009 at 3:42 PM, Zdenek Kotala<Zdenek(dot)Kotala(at)sun(dot)com> wrote:
> > Josh Berkus píše v st 01. 07. 2009 v 17:21 -0700:
> >> Folks,
> >>
> >> There's been a lot of discussion/argument around how to handle the last
> >> commitfest, but there seems to be a total consensus that we want to have
> >> the first CF on July 15th.
> >
> > Can we add flags like bump catalog version, bump page layout version,
> > modify AM for each patch? It should help to track pg_upgrade changes.
>
> That's not a bad idea, and it wouldn't be hard to add various flags
> and things to the CommitFest app I wrote, but how would we maintain
> the information and keep it correct? It seems like there might be a
> danger that patch authors wouldn't know whether or not they were doing
> those things. Also, how would we handle changes by committers, who
> don't always go through the CommitFest process?
I think this information could be computed automatically, if someone cared
enough. It shouldn't be necessary to bother every single participant in the
process with this.
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2009-07-03 06:41:25 | Provide support for multiplexing SIGUSR1 signal |
Previous Message | Dimitri Fontaine | 2009-07-03 06:15:45 | Re: PGXS problem with pdftotext |