I was wondering if removing these translations could be seen as a BC break because technically they have already been part of stable releases and theoretically could have been used by developers in their applications. Are we fine with that?

I was wondering if removing these translations could be seen as a BC break because technically they have already been part of stable releases and theoretically could have been used by developers in their applications. Are we fine with that?

It cannot be a BC break as 7.3 stable has not been released yet.

It cannot be a BC break as 7.3 stable has not been released yet.

What I mean is that the translations have been part of the 6.4.18+/7.1.11+/7.2.3+ releases and one could just use them with their own constraints or passing them directly to the translator without needing the actual Slug constraint. 🤷‍♂️

It cannot be a BC break as 7.3 stable has not been released yet.

What I mean is that the translations have been part of the 6.4.18+/7.1.11+/7.2.3+ releases and one could just use them with their own constraints or passing them directly to the translator without needing the actual Slug constraint. 🤷‍♂️

Sure, I understand that. Still, I don't think this should be considered as a BC break as we're adding translations on 6.4 just to ease our work.

Maybe we should add this to our BC promise definition?

Sure, I understand that. Still, I don't think this should be considered as a BC break as we're adding translations on 6.4 just to ease our work.

Works for me, I agree with Oskar though that it might make sense to add this to our BC promise.

I created an issue

• Mention translations are not covered by BC promise symfony-docs#20980