>
> Current distance between fixes and main is about 13739 revisions. (not
> counting the 23 fpcbuild revisions, and the work that needs to be done
> for docs). Of course a MR can be more commits/revisions, but rarely more
> than 20. So 100 merge requests is at most 2000, and that is already a
> stretch, both wrt commits/mMR and that that already assumes that are
> most are viable to merge and will be eventually merged.
>
> You make a fair empirical point, and I genuinely do not know the
> answer either. It would be worth someone running that comparison
> before we treat the MR backlog as the primary symptom.
>
This is really interesting! I analyzed the open MRs and posted the results on
the bug tracker (GitLab allows for good formatting/linking/editing):
https://gitlab.com/freepascal.org/fpc/source/-/work_items/41722
The first rows of the table are very small MRs that can be reviewed and
resolved quickly. This could potentially help close a dozen or so MRs at once.
The table also clearly shows "abnormally" large and empty MRs — I've already
submitted comments on some of them (looks like a merge/rebase error).
Later, I'll be able to compare their total size with the difference between the
main/fixes branches. Frankly, I don't think "commit" is a good unit of
measurement, so I counted the number of "changed lines". But the number of
commits could also be taken into account.
_______________________________________________
fpc-devel maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
