Symfony 3.4 for v2

[soullivaneuh]

This issue is more an interrogation than a problem. 😉

Why dropping the support of Symfony v3.4 for the next major version?

AFAIK, v3.4 is exactly the same as v4.0 but with the deprecated methods in addition, so it should not be a problem at all to support both.

Plus, it will allow you to support at least one Symfony LTS version.

WDYT? Maybe I'm missing something? 🤔

Regards

[javiereguiluz]

I've been thinking a lot about this. The thing is that we are not Symfony and we don't have their resources 😭. The BC policy of Symfony is amazing and I'd love to do the same here, but we can't. So, I prefer to be realistic and the policy I'd like to follow is the same as ApiPlatform (api-platform/docs#405):

	New Features	Bug Fixes	Security Fixes
master	x	x	x
master - 1		x	x
master - 2			x

---

So, I want to create the 2.0 branch as soon as possible and release 2.0.0 version (requires PHP 7.1 and Sf 4.0). Then, work on the new features in master and soon after Sf 4.1 is released in May, release 2.1.0 (requires PHP 7.1 and Sf 4.1).

So, in May we'll have:

• 1.x branch: security fixes only
• 2.0 branch: bug fixes + security fixes
• master branch: features + bug fixes + security fixes

---

As it happened to Symfony when it changed its release policy, we could make an exception in the case of 1.x and keep fixing some important bugs until the end of Nov 2018, when 2.8 support ends.

---

I can understand if someone is disappointed, but this is not a commercial project, se just do the best we can. Also, there's Sonata as an alternative admin generator with more features and probably better long term support.

[c33s]

@javiereguiluz it is really sad but i can understand it. what i can't understand is the rush for symfony 4.1 #2390 and the hard enforcement. as 3.4 is compatible with 4.0 it should work for v2 out of the box (assuming the sf4 directory structure and flex is used)

you don't have to officialy support 3.4 but it would help if you don't block it. so people can gather and help supporting it.

and no sonata is not an alternative for easyadmin :)
there is a reason why easyadmin is the "official" admin for symfony (so i think it would be really important to support lts releases of symfony).

maybe someone from symfony/sensio can help to make easyadmin more official and therefor better supported