Add MAGETWO-67805 as a known issue to the release notes

[korostii]

Feedback on page: /guides/v2.1/release-notes/ReleaseNotes2.1.6CE.html

There seems to be a bug introduced by the version 2.1.6
It is reported in magento/magento2#9385 and magento/magento2#9395 , and it recently got an internal ticket MAGETWO-67805

Please add info about it to the release notes as a "Known issue" in order to warn the merchants and integrators about this possible issue. IMHO that would also somewhat prevent more and more new github issues reported about it (not as much as a fast patch, but still).

Haven't tested if the following workaround is working, but if it is - it might be worth mentioning as well

To not have Magento do this, you now have to include <frame>0</frame> within that image definition in view.xml

[jfrontain]

@korostii, we are working on a technical bulletin to describe this issue and its workaround, and will publish shortly. Thanks!

[korostii]

Thanks for your timely response. For reference, here's a link to that newly published page: http://devdocs.magento.com/guides/v2.1/release-notes/tech_bull_216-imageresize.html

However, comments on #9395 indicate that the workaround from #9385 doesn't help to resolve the other issue.
Please update the bulletin when\if core team has any updates on the issue.

[jfrontain]

@korostii, thanks again. We're working on refining the workaround, and we'll update the technical bulletin as soon as possible.

[jfrontain]

@korostii, I am closing this issue now. We updated the workaround to the best of our abilities last year and hope that users have upgraded to a more recent version of 2.1.x by now. Thanks, as always, for your thoughtful and always helpful suggestions.