[Interest] Let's talk about the upcoming Camera breakage in 5.4.2

[Jason H]

 I wanted to open this discussion up to anyone who is using a Camera, who has working code in 5.4.1.

Brief backstory:
At 5.4.1 introduced a fix that is is being removed in 5.4.2, because it is considered a "behavior" change and not a bug fix. I think this categorization is wrong, and I'm going to explain why.
The change pertains to the EXIF rotation header. So if you capture in portraid mode, or upside down, Qt is aware of it. In 5.4.2, this is being removed.

The removal of this orientation flag mean now that images won't be captured correctly, as they will have the incorrect aspect ratio from what you expect. This has a rippling effect in that no longer can you capture a picture pf the preview and display it pixel-for-pixel on a subsequent screen. It is not just a rotation issue. I've done the rotation fix (which is quite simple) and it messes more things up than that. This causes additional code to be written by Qt customers to target 5.4.2 specifically.

But here's the kicker. The orientation is being put back in to 5.5. Meaning that customers who were looking for a few bug fixes in 5.4.2, will have to write additional code for one version of Qt, then back it out for 5.5. I think for all the customers doing camera capture on 5.4.1 (I assume this is all of the customers using camera capture) we will need to write code on 5.4.2, then back it out. 

Ideally, I'd like to get the EXIF orientation put back into in 5.4.2.
I'd like to propose a compromise, if we can't get EXIF orientation reinstated in 5.4.2. Which is addition of a flag to use orientation or not. This way we can have both ways. But this would be an API change and likely be dis-allowed from the start.  I want to make sure that all Qt users know of the upcoming breakage in Qt 5.4.2 and are available to release their concerns, so that the Qt team knows the extent that people will be pissed off from the change. If it's just me, then fine, I will accept that, but anyone doing camera capture on 5.4.1 should be concerned about this change.

If in fact the Qt does decide to break the "proper" behavior ,(since it's going to be in 5.5 after all!) then Qt users need to be given a turn-key fix to support 5.4.2 in the interim. It isn't proper that we have to scramble for fixes for a x.x.Y release when we know it is temporary breakage.

Thank you and please chime in.