The C++ Driver Stable ABI will be available for experimental use in the upcoming release. As part of this effort, major breaking changes have been made to the unstable ABI, as was and is permitted by the ABI stability policy.
Users upgrading to the next upcoming release (4.2.0) should be:
encouraged to consider migrating to use the stable ABI (v1) in their code,
reminded that the unstable ABI (v_noabi) is not a stable ABI: recompilation has been and is still required for this upgrade, and
to report any observable API breaking changes (which there shouldn't be) so they can be reverted or addressed promptly.
The C++ Driver Stable ABI will be available for experimental use in the upcoming release. As part of this effort, major breaking changes have been made to the unstable ABI, as was and is permitted by the ABI stability policy.
Users upgrading to the next upcoming release (4.2.0) should be:
encouraged to consider migrating to use the stable ABI (v1) in their code,
reminded that the unstable ABI (v_noabi) is not a stable ABI: recompilation has been and is still required for this upgrade, and
to report any observable API breaking changes (which there shouldn't be) so they can be reverted or addressed promptly.