Re: Include patch id in commitfest page

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Include patch id in commitfest page
Date: 2025-01-12 23:11:49
Message-ID: CAGECzQSNNwGfY7cmPyQfczPQ1JPZZTAesgXngiwC9Y8KRsC=Fw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 11 Jan 2025 at 10:40, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> I want to register that I'm not a fan of this change:

Thanks for the feedback. Much bigger changes are coming soon (spoiler:
cfbot integration). Feedback is definitely welcome on those changes
too.

> Rationale: It puts the least important information first. For the most
> part, the CF entry number is irrelevant, so it shouldn't be shown in
> such a prominent position.

Fair enough. I think the main reason the entry number is not
irrelevant to me, is because it's the id that the cfbot uses. So when
fixing issues in either the cfbot or the cfbot integration the number
is my reference. (it's also the only stable reference in general,
because people sometimes change the title)

> Maybe
>
> <a>title here</a> (number here)
>
> would be a compromise.

That would work for me, but I think I'd probably prefer a separate
column then. I'll play around a bit.

> I would suggest that the actual fix would be to order by title instead
> of ID.

I don't think that should be too hard to do.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-01-12 23:55:24 Re: Pgoutput not capturing the generated columns
Previous Message Peter Geoghegan 2025-01-12 22:43:57 Re: Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST