Problem/Motivation

As discussed in #2395443: [policy, no patch] Follow symfony 2.7 or 3.0., this is the question we maybe switch over to symfony 3.0.x at some point.
In order to be able to do that, you need a way to ensure that nothing is broken, when we update.

Proposed resolution

Continuously try to update to symfony 3.0.x to see what BC apis we should try to replace with new ones,
where symfony 3.0.x maybe introduces new bugs etc.

Blocking issues:

Remaining tasks

User interface changes

API changes

Comments

dawehner’s picture

Issue summary: View changes
dawehner’s picture

While doing that I need to open a couple of issues against symfony, see IS.

rcross’s picture

With Symfony 3.0 released today, is this the best issue to start putting issues/patches?

rcross’s picture

dawehner’s picture

dawehner’s picture

Status: Active » Closed (duplicate)