Op 3-4-2026 om 20:21 schreef Florian Klämpfl via fpc-devel:
Multiple reasons:
- it’s a boring job
- fpc releases require an awful amount of handwork like updating version
numbers in multiple files like readmes, whatsnew, utils etc.
- tracking progress is documented in the wiki, another pain
- FPC repository structure directly converted to git make working with it a
nightmare: git sub modules reference to a certain revision, so when something
is updated in a release branch of fpcsrc, the „super“ module (i.e. fpcbuild)
needs an update as well, makes working very messy. In principle sounds doable,
in practice one messes up permanently, in particular when working on multiple
machines and with multiple repositories.
- lack of time
IMHO it lacks the major one.:
- actually making sure the branch contains all must have fixes and
revisions it should have.
P.s. can we open the fixes branch for merging again? A 1 1/2 year freeze
makes it a bit stale.
_______________________________________________
fpc-devel maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
