On 16.06.25 14:47, Jelte Fennema-Nio wrote:
> And our already well-known commitfests for PG19 will be called as follows:
>
> - PG19-1 (previously 2025-07)
> - PG19-2 (previously 2025-09)
> - PG19-3 (previously 2025-11)
> - PG19-4 (previously 2026-01)
> - PG19-Final (previously 2026-03)
>
> The dates will be the same, the name will simply not be of the
> {year}-{month} format anymore. The actual dates will still be easily
> visible though. So the intent is that no-one loses information, but
> instead people will gain information because it's clear what Postgres
> version a commitfest is about.
Can you explain the motivation for this change a bit more?
I think I kind of like the calendar hints that the previous naming
gives. You can estimate how long ago something was or how long you
still have to finish or prepare something. The release number isn't
that meaningful, and the numbering withing the release less so.
Also, I wonder if this scheme would cause confusion about the question,
when and where am I allowed to submit patches for PG20? Would that go
into, say, PG19-4 or into PG20-Drafts?
Actually, even as I'm typing this message, I'm mentally confusing PG19-3
with "March". The number "3" just has these connotations of aaah,
better get it done. ;-)
