[fpc-devel] [RFC] Modernising the FPC Release Process -- Proposal for Review

[Marco van de Voort]

Op 18-4-2026 om 15:18 schreef Michael Van Canneyt via fpc-devel:
>
> It is about MR from 3rd party.
>
> My point was that since we have gitlab, the merging of user contributions
> goes way faster than the SVN+Mantis procedure, where we had to 
> download and apply patches manually. Anyone denying that is denying 
> the light of the sun.

Still that is different than the proposal.

1. it does not affect normal committers. Those never submitted branches 
as loose patches.

2. regular commiters like Rika, Margers etc already had gotten SVN 
access and/or branches in the past .

3. So that leaves the much smaller rest external contributors,.

That doesn't mean it is not an advantage/easier, but it must not be 
bigger than it really is.

And that is only the MAIN angle, for FIXES, an even again much smaller 
number is non compiler in easy to merge categories. Compiler is hardly 
merged any more after the initial major release.

>
> Given the amount of work I do on MRs, if I can flag and later or 
> immediatly merge MRs to a fixes branch, it would be a huge time saver.

So maybe 50 of your MRs apply, saving 50 times git cherry-pick -x over  
several years. Is that really worth changing all workflow over ? Do 
really think that will do anything wrt 5 year release gaps? Come on!

And _I_  (and some others like Pierre) do most of that (main->fixes)  
work now, and the bulk work is not really related to the release 
process. Only last minute stuff is.

So there are no huge numbers to accelerate in the first place.