Peter Eisentraut <[EMAIL PROTECTED]> writes:
> 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
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
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I suggest two redirects CommitFestInProgress and CommitFestOpen, and
> turning CommitFest into a plain page with suitable text pointing to both
> redirects.
> We'd also need a page saying "there is no commitfest currently in
> progress; maybe you wanted
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
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" an
