<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>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.</p>
<p>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).</p>
<p>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.</p>
<p>Kit</p>
<div class="moz-cite-prefix">On 06/04/2026 19:58, Juha Manninen via
fpc-devel wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f93910eb-30c1-4b4f-b261-0bcd2117eac2@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Kostas Michalopoulos via fpc-devel
kirjoitti 6.4.2026 klo 15.42:<br>
</div>
<blockquote type="cite"
cite="mid:31b4da70-3d34-4cd0-aa88-42c436d08de4@gmail.com">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.</blockquote>
<p>"<i>release cycle may need tweaks</i>"... For God's sake
Kostas, why you repeat that mambo-jambo? Those same things have
been repeated year after year after year.</p>
<p>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.</p>
<p>Help has been offered, first in forum threads, now here by
Graeme. FPC developers are not interested apparently.</p>
<p>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.</p>
<p>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.</p>
<p><br>
</p>
<p>Regards, Juha</p>
<p><br>
</p>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
fpc-devel maillist - <a class="moz-txt-link-abbreviated" href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel">https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel</a>
</pre>
</blockquote>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /><table style="border-top: 1px solid #D3D4DE;"><tr><td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://s-install.avcdn.net/ipm/preview/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;"/></a></td><td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free.<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a></td></tr></table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>