Re: About that CommitFest redirect page ...

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: About that CommitFest redirect page ...
Date: 2008-09-07 20:41:45
Message-ID: 200809072341.46630.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> So according to
> http://wiki.postgresql.org/index.php?title=CommitFest&action=history
> there's been rather a lot of confusion about where the CommitFest
> redirect page should point when.
>
> I think the problem is that we need two redirect pages: one for "the
> place where you should submit a new patch" and one for "the commitfest in
> progress". The problem is to choose names that will make it reasonably
> obvious which is which.

Well, when it is commitfest right now, I would like to be able to go to a URL
that says "commitfest" and then monitor and work on the things there. Most
people should be doing that.

The use case for adding things to the next commitfest while a commitfest is
currently happening much less convincing. Why would you submit a patch now
when you still have two months to work on on it and you should be reviewing
other patches anyway?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-09-07 20:52:12 Move src/tools/backend/ to wiki
Previous Message Tom Lane 2008-09-07 19:52:47 Re: reducing statistics write overhead