summaryrefslogtreecommitdiff
path: root/template/commitfest_search.tt2
diff options
context:
space:
mode:
Diffstat (limited to 'template/commitfest_search.tt2')
-rw-r--r--template/commitfest_search.tt217
1 files changed, 12 insertions, 5 deletions
diff --git a/template/commitfest_search.tt2 b/template/commitfest_search.tt2
index ab34187..9a14dd6 100644
--- a/template/commitfest_search.tt2
+++ b/template/commitfest_search.tt2
@@ -1,9 +1,16 @@
-<p>If you want to submit a new patch for review, please visit the <b>Open</b>
-CommitFest. If you want to help with the reviewing process for the
+<p>If you have submitted a patch to pgsql-hackers and want it to be reviewed,
+you should add it to the <a href='/action/commitfest_view/open'>Open
+CommitFest</a>. If you want to help with the reviewing process for the
CommitFest that's currently taking place (if any), please visit the
-CommitFest <b>In Progress</b>. Previous CommitFests are marked as
-<b>Closed</b>, and scheduled upcoming CommitFests (other than the one to which
-patches should be submitted) are marked as <b>Future</b>.</p>
+<a href='/action/commitfest_view/inprogress'>CommitFest In Progress</a>.
+These links are stable and always reference the open or in progress
+CommitFest, respectively, provided such a CommitFest exists. (If there is no
+CommitFest in progress, the CommitFest In Progress link will reference the
+Open CommitFest instead.) There is also a stable link for the
+<a href='/action/commitfest_view/previous'>Previous CommitFest</a>, meaning
+the most recent one that is now marked Closed. Upcoming CommitFests
+(other than the one to which patches should be submitted) are marked
+as <b>Future</b>.</p>
[% IF list.size == 0 %]
<p><b>No CommitFests have been defined yet.</b></p>