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

[Michael Van Canneyt]

On Fri, 17 Apr 2026, Marco van de Voort via fpc-devel wrote:

>
> Op 17-4-2026 om 11:57 schreef Michael Van Canneyt:
>>
>> It does: By better structuring - for example forcing the use of a MR -
>> we can assign a milestone when accepting MR's and we'll have an exact
>> list of MRs to go to fixes as well as devel.
>>
> /So much/ administrative overhead. And then we still have to find out if 
> that concept works at all in the FPC context.

There is no administrative overhead. I'mm not proposing to work with epics,
stories and whatnot.

No: You create a branch, develop your thing, and push. That's it. 
Press a button to merge.

The difference with before: we have a good record that's easier to handle.

And if we find it really does not work, we switch back. It's that simple.

> I would be against that.

No surprise there.

We see the world very differently. As far as I am concerned, the change to
gitlab has only been for the good. The number of merged merge requests is a
testimony to that.

Your last words in your mail clearly indicate you have a different view of that.

Probably a matter of glass half full/half empty.

Michael.