[fpc-devel] 134 open merge requests - is that normal?

[Marco van de Voort]

Op 7-4-2026 om 10:59 schreef Michael Van Canneyt via fpc-devel:
> Timed releases make perfect sense in any context:
>
> Whatever is in, is in. What is not, goes in the next release. 

That's a snapshot, not a release.

>
> It's like a train schedule:
>
> If a fix catches the current train, great. Else it takes the next train.

With a train, they are staffed and sometimes even cleaned when they roll 
into the station.

It is an organised endeavour, not a mindless robo-act.

Moreover, even if, it would only work for minor releases.

>
> 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.
>
IMHO there would be robobuilds of fixes releases without much content, 
and it provides no solution for releasing the first release of a  branch 
at all.

If this all were this simple, nobody would complain about releases, and 
just use trunk/main snapshots.