Обсуждение: Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close

On Mon, 16 Jun 2025 at 14:47, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>
> The new PG19 development cycle is starting soon. So that seemed like a
> good excuse to make some big improvements to the commitfest app.

These changes have now been deployed to production. Please report any
problems, either as a reply or as a github issue.

Hi,

> > The new PG19 development cycle is starting soon. So that seemed like a
> > good excuse to make some big improvements to the commitfest app.
>
> These changes have now been deployed to production. Please report any
> problems, either as a reply or as a github issue.

Firstly, many thanks for working on this.

I don't see a button that would allow me to add a patch to PG19-1
(2025-07-01 - 2025-07-31). I tried to log out and log in but it didn't
change anything. Is it a bug or do I miss something?

-- 
Best regards,
Aleksander Alekseev

Hi,

> Fourth link down from the top of the link section - "Create a new commitfest entry"
>
> Adds it to 19-1; need to move it to Drafts if that is where it belongs.

Found it. It was moved to the "Your personal dashboard" page.
Previously I used the CF page thus I couldn't find it.

Many thanks.

-- 
Best regards,
Aleksander Alekseev

On Wed, 25 Jun 2025 at 20:29, Aleksander Alekseev
<aleksander@timescale.com> wrote:
>
> Hi,
>
> > Fourth link down from the top of the link section - "Create a new commitfest entry"
> >
> > Adds it to 19-1; need to move it to Drafts if that is where it belongs.
>
> Found it. It was moved to the "Your personal dashboard" page.
> Previously I used the CF page thus I couldn't find it.

Ugh... Turns out it was a bug, there definitely should be a "New
patch" button on both the 19-1 and on the Drafts page. And there
was... but only if you were logged in as a staff user.


I had changed a field name to from "isopen" to "is_open" and forgot to
change the usage in that template. Very annoying that django templates
not complaining about missing attributes...

Hi,

> Ugh... Turns out it was a bug, there definitely should be a "New
> patch" button on both the 19-1 and on the Drafts page. And there
> was... but only if you were logged in as a staff user.

There is now a "New patch" button on the CF entry page. Many thanks!

> I had changed a field name to from "isopen" to "is_open" and forgot to
> change the usage in that template. Very annoying that django templates
> not complaining about missing attributes...

Time to rewrite CF application in Haskell and Yesod? :D (Not
realistic, I know...)

-- 
Best regards,
Aleksander Alekseev

On Thu, 26 Jun 2025 at 03:21, Aleksander Alekseev
<aleksander@timescale.com> wrote:
>
> Hi,
>
> > Ugh... Turns out it was a bug, there definitely should be a "New
> > patch" button on both the 19-1 and on the Drafts page. And there
> > was... but only if you were logged in as a staff user.
>
> There is now a "New patch" button on the CF entry page. Many thanks!

I felt we can remove the "New patch" button from the Current CF page
as the commitfest is in progress, shouldn't the new patches be added
to PG19-2 commitfest.

Regards,
Vignesh

Hi,

> > > Ugh... Turns out it was a bug, there definitely should be a "New
> > > patch" button on both the 19-1 and on the Drafts page. And there
> > > was... but only if you were logged in as a staff user.
> >
> > There is now a "New patch" button on the CF entry page. Many thanks!
>
> I felt we can remove the "New patch" button from the Current CF page
> as the commitfest is in progress, shouldn't the new patches be added
> to PG19-2 commitfest.

It seems like cfbot.cputube.org started to miss a *few* entries since
CF started. Does it have anything to do with the CF application
update?

-- 
Best regards,
Aleksander Alekseev

On Wed, 2 Jul 2025 at 12:02, Aleksander Alekseev
<aleksander@timescale.com> wrote:
> It seems like cfbot.cputube.org started to miss a *few* entries since
> CF started. Does it have anything to do with the CF application
> update?

That's fixed now.

Hi,

> > It seems like cfbot.cputube.org started to miss a *few* entries since
> > CF started. Does it have anything to do with the CF application
> > update?
>
> That's fixed now.

Many thanks. I also noticed that cfbot doesn't show entries from the
*upcoming* commitfest. I believe it did before and according to the CF
application CI checks are executed for these patches, just not shown
on cfbot. Is it intentional?

On Mon, 14 Jul 2025 at 23:27, Aleksander Alekseev
<aleksander@tigerdata.com> wrote:
> Many thanks. I also noticed that cfbot doesn't show entries from the
> *upcoming* commitfest. I believe it did before and according to the CF
> application CI checks are executed for these patches, just not shown
> on cfbot. Is it intentional?

You can click the "Next Commitfest" button at the top [1]. I'm pretty
sure this has always worked like this.

[1]: https://cfbot.cputube.org/next.html