You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pgcommitfest/commitfest/templates/commitfest.html
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,12 @@
2
2
{%load commitfest %}
3
3
{%block contents%}
4
4
5
+
{%if cf.is_closed%}
6
+
<divclass="alert alert-warning" role="alert">
7
+
<strong>This commitfest is closed.</strong> Open patches in this commitfest are no longer being picked up by CI. If you want CI to run on your patch, move it to an open commitfest.
Copy file name to clipboardExpand all lines: pgcommitfest/commitfest/templates/help.html
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,11 @@ <h2>Commitfest</h2>
15
15
</p>
16
16
<p>There are 5 Commitfests per year. The first one is "In Progress" in <em>July</em> and starts the nine months feature development cycle of PostgreSQL. The next three are "In Progress" in <em>September</em>, <em>November</em> and <em>January</em>. The last Commitfest of the feature development cycle is "In Progress" in <em>March</em>, and ends a when the feature freeze starts. The exact date of the feature freeze depends on the year, but it's usually in early April.</p>
17
17
18
+
<h3>Commitfest closure</h3>
19
+
<p>
20
+
When a Commitfest closes, patches that have been active recently are automatically moved to the next Commitfest. A patch is considered "active" if it has had email activity in the past 30 days and has not been failing CI for more than 21 days. Patches that are not automatically moved will stay in the closed Commitfest, where they will no longer be picked up by CI. Authors of such patches that have enabled "Notify on all where author" in their profile settings will receive an email notification asking them to either move the patch to the next Commitfest or close it with an appropriate status.
21
+
</p>
22
+
18
23
<h2>Patches</h2>
19
24
<p>
20
25
A "patch" is a bit of an overloaded term in the PostgreSQL community. Email threads on the mailing list often contain "patch files" as attachments, such a file is often referred to as a "patch". A single email can even contain multiple related "patch files", which are called a "patchset". However, in the context of a Commitfest app a "patch" usually means a "patch entry" in the Commitfest app. Such a "patch entry" is a reference to a mailinglist thread on which change to PostgreSQL has been proposed, by someone sending an email that contain one or more "patch files". The Commitfest app will automatically detect new versions of the patch files and update the "patch entry" accordingly.
Copy file name to clipboardExpand all lines: pgcommitfest/commitfest/templates/patch.html
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,13 @@
1
1
{%extends "base.html"%}
2
2
{%load commitfest%}
3
3
{%block contents%}
4
+
{%with current_poc=patch_commitfests.0%}
5
+
{%if cf.is_closed and not current_poc.is_closed%}
6
+
<divclass="alert alert-warning" role="alert">
7
+
<strong>This patch is part of a closed commitfest.</strong> It is no longer being picked up by CI. If you want CI to run on this patch, move it to an open commitfest.
0 commit comments