@66Ton99 IMO, you should have a single branch where new features are added. The current branching model is quite weird: you add new features in both 1.4.x and master, and the only difference between them is the composer constraint (while the same code could be used for Mink 1.4 and Mink 1.5).
It would be less maintenance work to use a single branch. And otherwise, the older branch should be put in maintenance mode (i.e. bug fix only, no new features)
@66Ton99 IMO, you should have a single branch where new features are added. The current branching model is quite weird: you add new features in both 1.4.x and master, and the only difference between them is the composer constraint (while the same code could be used for Mink 1.4 and Mink 1.5). It would be less maintenance work to use a single branch. And otherwise, the older branch should be put in maintenance mode (i.e. bug fix only, no new features)