[fpc-devel] [RFC] Modernising the FPC Release Process -- Proposal for Review

[Michael Van Canneyt]

On Wed, 15 Apr 2026, Marco van de Voort via fpc-devel wrote:

>
> Op 15-4-2026 om 15:18 schreef Graeme Geldenhuys via fpc-devel:
>
> (warning: this will be harsh, as I'm increasingly getting fed up by 
> these gratuitous "release process" designers)
>>
>> The central idea is a "Release Train" model: releases depart on a
>> fixed schedule regardless of which features are ready, removing the
>> "just one more thing" pressure that has kept us in freeze. The
>> document covers:
>
> It is the exact opposite of my central idea. Which is "More release 
> workers, less release workflow designers". Specially not workflow 
> designers that never took any responsibility for the release project before.
>
> To anybody that wants to fix the release problem: be a manager for a 
> full major cycle. Then you can redesign the process. Not before.  And 
> yes, that includes you, Michael.

No worries there:

I already told Detlef Overbeek last weekend I would take up the
3.2.4 release task in July if Florian didn't find the time by then.
I have still 2 AI conferences where I must speak, but then there will be
time.

Graeme - or anyone else interested in moving things forward: 
I'm interested in ideas for making the CI/CD come up with 
release artifacts for the major platforms: windows, linux and mac.

Michael.