Re: Tags in the commitfest app: How to use them and what tags to add? - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: Tags in the commitfest app: How to use them and what tags to add?
Date
Msg-id CAGECzQQpu-O=M=cWW1_5EEUWB_Y7X3uNc-kyd6La7FO=xneE+w@mail.gmail.com
Whole thread Raw
In response to Re: Tags in the commitfest app: How to use them and what tags to add?  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Tags in the commitfest app: How to use them and what tags to add?
List pgsql-hackers
On Mon, 23 Jun 2025 at 18:29, Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> Initial thoughts:

below my reasoning (feel free to disagree).

> - "dblink" seems overly specific compared to the others.

It seemed roughly as specific as postgres_fdw to me. Maybe we should
make sure they are grouped more alphabetically.

contrib/dblink
contrib/postgres_fdw

(or in a different format like "Contrib - dblink")

> - "Backport" seems strange. That's what the Version column is for, no?

I still don't know how I'm supposed to use the version column (e.g.
what is the difference between stable and pg19), and it seems out of
date or not filled in half of the time. So I'd rather have it replaced
with tags with clear intent. Maybe have backport tags for each
Postgres version instead of "Backport - PG16" etc. The assumption
being, if it doesn't have a backport tag, then it should go into
master.

> - "Comments Only" feels somehow... standoffish? defensive? How about
> "Comments [Requested/Needed]" or something similar?

I meant this as "This patch changes only comments", the hover text
also explains that once selected.

> (Who added the existing ones?)

Me, as part of the database migration that added support for tags.



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
Next
From: "David G. Johnston"
Date:
Subject: Re: Tags in the commitfest app: How to use them and what tags to add?