MIME-Version: 1.0
References: 
 <CAGECzQTbHhaZMY-=Y=OGMU_jik4MqCfsc7rDf6AnT=Aq-B6cZA@mail.gmail.com>
In-Reply-To: 
 <CAGECzQTbHhaZMY-=Y=OGMU_jik4MqCfsc7rDf6AnT=Aq-B6cZA@mail.gmail.com>
From: vignesh C <vignesh21@gmail.com>
Date: Sun, 9 Mar 2025 07:50:54 +0530
Message-ID: 
 <CALDaNm2TjZLOE6u8n3ZZw23rLq=UUOKFwtO=WsVoGBd_7WJNRg@mail.gmail.com>
Subject: Re: Commitfest app release on Feb 17 with many improvements
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
	Jacob Brazeal <jacob.brazeal@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CALDaNm2TjZLOE6u8n3ZZw23rLq%3DUUOKFwtO%3DWsVoGBd_7WJNRg%40mail.gmail.com>
Precedence: bulk

On Fri, 31 Jan 2025 at 19:54, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
>
> At the FOSDEM dev meeting we discussed potential improvements to the
> commitfest app and how to handle deploying future changes with minimal
> disruption to existing workflows. We're going to try a new approach:
> announcing a new commitfest release ~2 weeks in advance, including
> release notes. That way people can try out the changes on the staging
> environment and raise concerns/objections. So hereby such an
> announcement:
>
> The next commitfest app release will take place on February 17 and
> will contain the following user facing changes:
>
> 1. Showing CFBot status on patch and commitfest pages

Couple of suggestions: a) No need to show CI status as "Needs rebase,"
"Not processed," etc., for committed patches. b) Can we add a filter
for "Needs rebase!"? This would help the CommitFest manager easily
list patches that need updating.

Regards,
Vignesh