Den ons 17 juli 2019 09:56Mathieu Westphal (Kitware) via VTK noreply@discourse.vtk.org skrev:
A good document, but I have reservations about certain points.
those changes should never cause user code to fail to compile
Too extreme imo. Deprecated code can be removed at some point.
As a user of VTK I think it would be nice if VTK followed an ABI/API compat and deprecation policy similar to Qt’s. That is, maintain compat across minor versions, but allow breaks across major ones, and have deprecation macros so that use of deprecated APIs show up as warnings for at least one minor version before being dropped in a major one.
It is of course up to you folks what kind of commitment you’re willing to make, and I understand if this would be a too big ask.
We’re one of those Kitware-external users who, unlike e.g. ParaView, do not track VTK master. But we try to follow each minor release. It would be nice if, like with Qt, we could be guaranteed an essentially painless upgrade when moving between minor versions.
Cheers,
Elvis