On 2026-04-17 10:57, Michael Van Canneyt via fpc-devel wrote:
Merging to devel and/or fixes branch is then much easier: it already groups commits that belong together.

By forcing a little more work upfront, we reduce the work later on, and we'll
not be stuck with a bazillion commits that no-one knows how to handle.

As I understand it, many people use the fixes_x branch, so it'll also be
tested a lot sooner.


I'm glad somebody gets it!!!


General observation:
From an outsider’s perspective, it appears there was a migration from Subversion to Git without a corresponding shift in workflow. Many team members seem stuck in a "Subversion mentality" -- the idea that branches are expensive or merging is difficult -- none of which applies to Git.

Unfortunately, the FPC project seems to have stalled since the migration, and there is no clear consensus on how to properly leverage these new [2026] tools. Given that, I don't believe there is much more I can contribute at this stage. I’ll stay on the sidelines for now and hope for the best. And yes, I'm still happy to triage/review Merge Requests where I can. Could we at least get some triage labels added to the fpcsource project, as I suggested in the proposal?

Regards,
  Graeme
_______________________________________________
fpc-devel maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply via email to