On Tue, 7 Apr 2026, Marco van de Voort via fpc-devel wrote:
Op 6-4-2026 om 23:43 schreef Graeme Geldenhuys via fpc-devel:
It also leads to a more buggy compiler though. FPC has great
stability and i think not making a release until the compiler
is stable enough is a good thing for end users.
Respectfully, I disagree that time-based releases inherently lead to more
bugs. In fact, the current 5-year gap since the 3.2.2 release is causing a
different kind of "instability" for framework developers and end-users.
Respectfully, I disagree. Time-based releases don't solve anything in the
current FPC context.
It works for a few large and heavily sponsored projects with heaps of grunts
that continuously do release engineering work anyway for their corporate
masters' internal trees. Then you only have to pick a moment, and that might
as well be on a clock, or by lobbing an arrow at a dart board.
Timed releases make perfect sense in any context:
Whatever is in, is in. What is not, goes in the next release.
It's like a train schedule:
If a fix catches the current train, great. Else it takes the next train.
in the end all fixes reach the destination:
The users get their desired updates on a regular basis.
Maybe not in this, but then in the next release.
Michael.
_______________________________________________
fpc-devel maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
