Ivan Voskoboinyk

> What do you think if we add a configuration parameter to activate this patch (to minimize any BC breaks)? If you ask me, I'd say this fix should live...

@alquerci Hey Alexandre, > ... because there is no way to provide this patch as a set of stock framework classes overrides. I might be wrong, but I see nothing...

In regards to existence of the FOS1 organisation, I believe the most important is to define the mission and the goals. Naming a few that come into my mind: -...

Good stuff :+1: > - Provide the most easier migration path to the latest Symfony version. > - Write a migration path documentation. However, I don't think it is feasible...

I'm not sure how many people really want to spend time on their sf1 projects and upgrade/migrate those projects to a new Symfony version. Most probably people are just looking...

@mbrung is your app under active development or is it just a legacy project requiring maintenance?

@mkopinsky FWIW we at @prezly are maintaining a fork of sf1, which has been slowly moving forward (mainly by shaking off old functionality that, as we believe, is better to...

If anyone's interested, we at @prezly maintain our own fork of symfony1, which has been moved forward from 1.4 It's https://github.com/rock-symphony/rock-symphony

@alquerci this is the time to close it, I guess.

I've just bumped into the same issue. `turbo` + `typescript` composite project (which forces incremental builds).