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

[J. Gareth Moreton]

While I agree it would be nice to see a new release soon, releasing a 
new version for the sake of releasing a new version I wouldn't recommend 
if it contains features that are half complete.  No need to be rude 
about things.

Believe me, as an FPC developer I am trying to fix bugs and get some new 
features introduced into the compiler, like pure functions.  While I 
have merge rights, I'm wary about merging big additions lest there are 
bugs that I've overlooked (hence the need for code reviews, although 
sometimes I can't change what they request and have to try to justify 
it).  Also my focus is on code generation and peephole optimisation, so 
anything involving packages and other components I tend to not review 
unless it's something fairly simple (I've also only started to review 
other people's code at my own volition).

You're welcome to create your own fork of Free Pascal, as per the GNU 
General Public Licence - believe me, I was tempted to at one point as 
well because of my focus on low-level optimisation conflicting with the 
cross-platform nature of the compiler somewhat.  I've worked around that 
since with better code generation.

Kit

On 06/04/2026 19:58, Juha Manninen via fpc-devel wrote:
> 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
>
>
>
> _______________________________________________
> fpc-devel maillist  -fpc-devel at lists.freepascal.org
> https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20260406/8ef94513/attachment-0001.htm>