On 3/5/25 12:14 AM, Jelte Fennema-Nio wrote:
> On Tue, 4 Mar 2025 at 22:01, Andreas Karlsson <andreas@proxel.se> wrote:
>> What I need to see is the below (plus any future commit fests).
>
> Thanks you for describing how you use the current homepage. That's
> super helpful.
>
>> I am interested in the dates when commit fests open and close
>
> These are the same exact 5 months every year. Maybe the homepage
> should contain some basic, mostly static, info at the top like:
>
> There are 5 commitfests for each PostgreSQL release. They take place
> in the months July (the first of the development cycle), September,
> November, January and March (the last before the feature freeze). A
> commitfest lasts for the full month. Patches can be submitted to a
> commitfest before that month has started. After a commitfest has
> started new patches need to be registered for the following
> commitfest. The .../No commitfest is currently in progress. The next
> commitfest starts on ...
Yup, and I and other (in my case formerly; since this January)
non-professional PostgreSQL developers have no chance to remember when
the commit fests are. And I suspect some of the professionals don't
always remember. :) And this is data I have often wanted.
>> and to be
>> able to quickly navigate to the open, the in progress and the latest
>> closed one.
>
> Could you elaborate why you want to navigate to the latest closed one?
> Is that to move your own patches (or ones that you are reviewing) over
> to the next one? If so it sounds like that would not be necessary
> anymore with the new dashboard page. If you have some other reason I'm
> very curious to know.
Yes, to move patches over to the next commit fest.
Andreas
