Workflow Change

Last week, we made a big decision regarding how we manage our dependencies. Until now, our policy was to never drop support for old versions of our dependencies in a stable branch, although we knew full well doing so complies with Semver. But the thing is, having that kind of constraint is a burden for both maintainers and contributors: maintainers have to ensure the build stays green on a wider range of versions, and contributor have to write more complex statements to handle all the supported APIs of our vendors. Both have to wait longer for builds to end. Unlike the team behind Symfony, we are a very small team and decided that our time and energy would be better spent elsewhere.

The new policy

Starting today, we only commit to support actively maintained versions of php, which can be seen as green on this chart. Regarding Symfony, we commit to support the latest LTS and all versions that are maintained and are not an LTS version.

But rules are meant to be broken, and since we already dropped support for php 7.0 on some master branches of our packages, we elected to exceptionally drop it on the stable branches too, given that 7.0 is nearly reaching its end-of-life period.

To sum it up, we are currently dropping php 5.3 to 7.0 and symfony 2.3 to 2.7 on all maintained branches of our packages. Hopefully this will allow us to move faster and deliver major versions more often.

Comments

  • No comments available

Leave a comment