Re: Commitfest app release on Feb 17 with many improvements
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Álvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Jacob Brazeal <jacob.brazeal@gmail.com>
Date: 2025-02-18T21:15:11Z
Lists: pgsql-hackers
On Tue, Feb 4, 2025 at 05:27:18PM +0100, Álvaro Herrera wrote: > On 2025-Jan-31, Jelte Fennema-Nio wrote: > > > 3. Showing total additions/deletions of the most recent patchset on > > patch and commitfest pages > > 4. Showing additions/deletions of the first patch of the most recent > > patchset on the patch page > > 5. Showing the version and number of patches of the most recent > > patchset on the patch page > > I think this has potential for excessive clutter. I propose that, if > we're going to have a column with addition/deletions, we have two > things: > > 1. the total number of addition and deletions in the whole patch > series, for the last patchset version posted. This would be shown in > the column. > 2. a per-patch breakdown of the number of addition and deletions for the > last patchset version posted, one line per patch. This would appear > in a tooltip on the column for the totals, to avoid interface > clutter. > > > 10. Allow sorting patches by total additions/deletions (added together > > for total lines changed) > > Seems reasonable, though I don't see much of an use-case for this. Looking at the live version, I can sort the "Stats" column from smallest to largest, but not from largest to smallest. Is this intended? -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.