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

Tomas Hajny XHajT03 at hajny.biz
Thu Apr 16 00:30:50 CEST 2026


On 2026-04-16 00:06, Graeme Geldenhuys via fpc-devel wrote:


  .
  .
> If that role is not something the team is comfortable handing
> to someone outside the core group, I understand. There is still
> plenty I could help with: setting up the triage label workflow,
> improving the CI pipelines, or simply keeping the process
> documentation up to date. The intent throughout is to reduce
> friction for the people doing the real work, not to add to it.
  .
  .

As somebody having been involved in that role in the past (see 
https://wiki.freepascal.org/Release_Template and e.g. 
https://wiki.freepascal.org/Release_2.0.4), I can say for sure that the 
release coordinator / release master / ... certainly doesn't need to 
know all the details of the compiler, RTL and everything else at the 
same time :-) - this isn't the issue. From my experience, making sure 
that people who can tackle specific tasks blocking the release (should 
it be particular manual steps in the release building process, or fixing 
some issue which popped out during the build), find needed time for 
addressing the needed things, is the biggest obstacle.

BTW, are you aware of the Release engineering page on our Wiki 
(https://wiki.freepascal.org/Release_engineering)?

Tomas


More information about the fpc-devel mailing list