Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close

On Wed, 18 Jun 2025 at 05:58, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> Can you explain the motivation for this change a bit more?

A few main reasons (from important to unimportant):
1. For new/irregular contributors the old names were really not
obvious IMO. It took me 3+ years to get the mental association with
March, that that was the final one for the release.
2. Looking up a historic patch from the mailinglist in the CF app,
should now give you a good idea what PG version it got in. (e.g. Oh,
AIO support got committed in PG18-Final)
3. The March commitfest is actually not just March, it ends at the
feature freeze. Which again is not obvious for many irregular users.
4. For the Draft CFs we needed a new naming scheme, and this aligns
nicely with it.
5. It's a little bit shorter

> I think I kind of like the calendar hints that the previous naming
> gives.

To be clear, this new naming scheme is definitely up for discussion.
It's easily changeable/revertible/tunable. However, unless there's an
overwhelming negative response to this email thread about this, I
think it's worth trying out. If it's not to people's liking after
trying it out for a while (e.g. after one or two commitfests), then we
can still easily change the names back to the old scheme (even of
already created/closed commitfests).

> 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.

To be clear, I did not intend to make this harder to find out.. The
dates are still visible on the homepage, just next to the name instead
of in the name. I realized now, they are indeed missing in a few other
places. Specifically the title of a commitfest page, and the patch
page. I fixed those now, if you find other places please let me know.

> 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?

I don't think this will be a problem in practice. PG20-Drafts and
PG20-1 will open at the same time: 1st of March. Before that time
people will only be able to submit to PG19-Drafts and PG19-X (with X
depending on the time of year).

> 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. ;-)

Yeah, I totally get that, there's definitely some trained stress about
the number 3 for me too. But as explained in my number one reason for
the change, new users don't have that stress yet. I think Final has
those stressful connotations more naturally (and I expect getting used
to Final shouldn't be too hard for you either).