[fpc-devel] 134 open merge requests - is that normal?

[Juha Manninen]

Kostas Michalopoulos via fpc-devel kirjoitti 6.4.2026 klo 15.42:
> FWIW i agree that the release cycle may need tweaks, but i think it 
> should be based on what bugs/tasks are to be fixed/done for a release 
> and come whenever those are fixed/done, not in fixed timesteps - 
> especially since FPC relies largely on volunteer work who work in 
> their free time. It isn't like the FPC devs have a bunch of MBA's with 
> quarterly growth goals to please :-P.

"/release cycle may need tweaks/"... For God's sake Kostas, why you 
repeat that mambo-jambo? Those same things have been repeated year 
after year after year.

None of the FPC development team seems to have any intention to make a 
release. The release manager here asks "Who will build the release". He 
has no idea. The whole team has clearly dropped the ball. They have time 
to write posts and messages to explain why a release is not possible. 
They could have released many versions already with that energy.

Help has been offered, first in forum threads, now here by Graeme. FPC 
developers are not interested apparently.

Lazarus project and many FPC users are in dire need for a release and 
then more releases in reasonable time intervals. I see forking the FPC 
project as a more and more compelling option. The fork would concentrate 
on timely releases. Lazarus would officially support the fork, then it 
could become popular. It would need a dedicated team. The first task 
could indeed be to automate the release build process.

My prediction is that after one year from now there still is no new 
release, based on the attitude of FPC developers. Would people then 
agree with the forking idea? Start to think of names for the fork.


Regards, Juha

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20260406/528c262c/attachment.htm>