We have a clear development policy that says that features must be hidden behind feature flags and technical analysis of the proposal clearly indicated that such a flag would be needed as there are fears of performance regression. In such situations, things never just appear in production without a plan. Besides, was "deploy it to production" part of acceptance criteria?

We have a clear development policy that says that features must be hidden behind feature flags and technical analysis of the proposal clearly indicated that such a flag would be needed as there are fears of performance regression. In such situations, things never just appear in production without a plan. Besides, was "deploy it to production" part of acceptance criteria?

Well, you wrote that ticket. It didn't explicitly say anything and I assumed that deployment would be a part of that ticket. We don't always have separate tickets for deployments. Nevertheless, my question about deployment dates still stands. I'm responsible for communicating with the community about this feature and doing the QA work on it so it would be helpful to me to know when you plan to put this out.

@MaxSem Right. I am assuming that the production impact will theoretically be caused by the computation which decides which language to generate the image in. If that assumption is correct, do images which are added with an explicit lang flag not cause a performance impact? Or it is caused for all images irrespective of the presence of the lang flag? If that assumption is incorrect, what part of the process is expected to cause a performance impact?
I hope my question is clear.