Re: Next commitfest app release is planned for March 18th

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>, Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com>
Subject: Re: Next commitfest app release is planned for March 18th
Date: 2025-03-04 19:46:34
Message-ID: A97DA272-78AB-4A90-9F54-950F8B834F89@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 4 Mar 2025, at 17:13, Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
> On Tue, 4 Mar 2025 at 16:29, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:

>> Another small complaint: I don't like this style of relative times. (I
>> have also complained about it for the buildfarm status in the past.) I
>> suppose both styles are useful like 50% of the time, but I'll tell you
>> some of my reasoning:
>
> So it's currently using Django its default "timesince" function. I
> think we can probably modify that a bit to fit better with the
> commitfest purpose.

My preference would be not have any relative times or dates at all and just
show the date as is.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-03-04 19:48:37 Re: Rename some signal and interrupt handling functions for consistency
Previous Message Nathan Bossart 2025-03-04 19:38:10 Re: Rename some signal and interrupt handling functions for consistency