You can optionally further organise patches within a section using subsections (Template:CommitFestSubSection). Subsections are usually used where there are several patches relating to a particular component or aspect of Postgres, and it is convenient for reviewers to have them listed together. So you might create a subsection called "psql" or "Performance".

In general, patches are listed in the same order they were added to the section or subsection. So, pending patches are listed in submission order, committed patches in commit order and rejected patches in the order they were rejected.

Reviewing items

If you are reviewing an item, let the other developers know by adding your name into the reviewers parameter of the patch. For example, if you started reviewing the following patch

Feature freeze

Update the arguments to the CommitFestNav template to reflect the new commitfest's position in the sequence. It's okay to leave the "next" argument empty until there is something to point at. Speaking of which, go back to the previous commitfest and update the "next" link there to point at the new page.

Modify any redirects (such as CommitFestOpen) to point to the new commitfest.