On Wed, 15 Apr 2026, Kevin Lyda via fpc-devel wrote:
On Wed, 15 Apr 2026 at 16:45, Martin Frb via fpc-devel <
[email protected]> wrote:
While (as outsider) I would welcome a "time"-ish based cycle, I don't
think it will work entirely.
You mention it works for the kernel. But the kernel does not have
regression forced by other products. (well, hardware can change, but
that is more new hardware to support gets added / hardware already
supported does not suddenly stop).
Sure. Comparing to the kernel isn't ideal. Comparing to another compiler
would make more sense. The Go team do a major (the second number) release
every 6 months and they support a large number of platforms. They do a
minor release (the third number) about once a month.
https://go.dev/doc/devel/release
It works rather well and helps teams using Go make plans for upgrades. I've
fully automated Go compiler upgrades in the past and it worked for years.
I do think a full CI system that builds the compiler for all supported
platforms and runs a test suite on each platform would help set folks minds
at ease.
Amen to that.
Michael.
_______________________________________________
fpc-devel maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
