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?