Feedback-ID: ie0a040ee:Fastmail
Message-ID: <8ba4e905-6045-4b7e-b4f7-4c9e3828ec8f@eisentraut.org>
Date: Thu, 19 Mar 2026 10:48:36 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Feature freeze timezone change request
To: Jelte Fennema-Nio <postgres@jeltef.nl>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>,
 rmt@lists.postgresql.org
References: 
 <CAGECzQSPzprMNguV6pA671kbSznNmufgqCQGNmpUm4VgdfLW-A@mail.gmail.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: 
 <CAGECzQSPzprMNguV6pA671kbSznNmufgqCQGNmpUm4VgdfLW-A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/8ba4e905-6045-4b7e-b4f7-4c9e3828ec8f%40eisentraut.org>
Precedence: bulk

On 19.03.26 00:07, Jelte Fennema-Nio wrote:
> I was notified that the tentative feature freeze timestamp is on the
> wiki[1] as: April 8, 2026 0:00 UTC-12
> 
> I request that the final feature freeze timestamp be set to 0:00 UTC,
> not 0:00 UTC-12. The comitfest app currently only supports dates as
> the start/end of a commitfest, not datetimes. By using 0:00 UTC I (or
> anyone else with admin access) can simply fill in the last day of the
> commitfest, and the commitfest will be automatically closed when that
> day ends in UTC.

I don't think the end of the commitfest and feature freeze need to be 
the same thing.  The commitfest might as well end on 31 March or 1 April.