Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close - Mailing list pgsql-hackers

On Mon, Jun 16, 2025 at 6:48 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>
> The new PG19 development cycle is starting soon. So that seemed like a
> good excuse to make some big improvements to the commitfest app. My
> plan is to deploy these changes on the 30th of June. So that we can
> start the new cycle fresh with these changes. As always feedback on
> these changes is very welcome. The below will contain some links to
> the staging environment both username and password for the http auth
> are "pgtest".
>

Huge thanks for the huge changes.

Coinciding tooling changes with a milestone in tool usage has
potential to disrupt both. But in this case, the things seem to be
working in the staging environment. So I hope the start of PG19-1
commitfest will be smoother and a better experience.

Some comments below.

>
> # Draft CF
>
> There's now an additional Draft CF. People can move patches there as a
> way of not forgetting about them. CFBot will rerun these patches less
> frequently (exact behaviour TBD). Draft CFs are never "In Progress"
> and are open until the final CF of the release cycle becomes "In
> Progress". So PG19-Drafts will close on February 28th 2026, and at the
> same moment PG20-Drafts will be opened.
>
> Big thanks to David G Johnston for the initial work on this feature,
> and early review/feedback on all my changes to it.

This is interesting. I liked the idea of making Draft CF link part of
the landing page. People can find draft patches easily in case they
want to try those out and labelling them as "Draft" will set the
expectations right.

>
> # Automated commitfest open/close/create
>
> Right now people manually have to open/close/create commitfests at our
> regular cadence. This now actually encodes this cadence in the app
> itself. A new open commitfest is automatically created when needed. As
> well as commitfests automatically getting started or closed. The only
> commitfest that's not fully automated is the last one of the cycle,
> since that ends when the feature freeze starts (and the feature freeze
> isn't always the same date). To handle that the RMT (or anyone with
> access) should change the enddate of the final commitfest in the admin
> interface to the new date. That will need to happen before March 31st.
>
> A *bikesheddable* change here is the names that the newly created
> commitfests get automatically. Given we now have a Drafts commitfest,
> it seemed reasonable to align the naming of the regular commitfests
> with that. The draft commitfest will be called:
>
> - PG19-Drafts
>
> And our already well-known commitfests for PG19 will be called as follows:
>
> - PG19-1 (previously 2025-07)
> - PG19-2 (previously 2025-09)
> - PG19-3 (previously 2025-11)
> - PG19-4 (previously 2026-01)
> - PG19-Final (previously 2026-03)
>
> The dates will be the same, the name will simply not be of the
> {year}-{month} format anymore. The actual dates will still be easily
> visible though. So the intent is that no-one loses information, but
> instead people will gain information because it's clear what Postgres
> version a commitfest is about.
>
>
> # New homepage
>
> The homepage is revamped. It now shows only "In Progress", "Open",
> "Draft" and "Previous" commitfests and it also shows names & dates for
> "Next open CF" and "Final CF of the release cycle". See homepage.png
> screenshot for details or go to
> https://commitfest-test.postgresql.org/

I like this as well. I feel "In Progress" doesn't convey that the
column contains the dates when the CFs are active. It can be easily
confused with "In progress" CF. How about just "Dates" or "Duration"?

>
> The full list of commitfests is still available at:
> https://commitfest-test.postgresql.org/commitfest_history/ This page
> is linked to at the bottom most link on the homepage.
>

All patches in the current commitfest
All patches in the open commitfest

Are those two needed anymore since the CF links are already available?

Create a new commitfest entry - if we are creating the CFs
automatically, is this link that useful? And it could be a button/link
in the Commitfest section itself just before or after the table of
relevant commitfests.

--
Best Wishes,
Ashutosh Bapat