On 4/5/26 1:51 AM, Graeme Geldenhuys via fpc-devel wrote:
It would be better to spend the limited time available on improving the efficiency of the release cycle instead. If a time-based release every six months becomes a "no-brainer," it results in less effort for the FPC team and more frequent releases for end-users—leading to more widespread usage and better feedback.
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. People who can and want to test the compiler to find any bugs can already use the main branch - which is decently stable too. Personally i'm using the main branch that i update occasionally as my "main" (:-P) version and only use 3.2.2 when i want to make sure the code compiles with it.
TBH i never saw the point of time-based releases, yes you get faster and more often releases but those releases are not necessarily of a good quality.
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.
Kostas _______________________________________________ fpc-devel maillist - [email protected] https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
