> There is no date set for that yet. Not even roughly. The earliest > release where the engine API can be removed is 4.0 but there was no > decision on when that version is going to be released and it was not > even decided which of the deprecated APIs are going to be removed in > 4.0. > The functions deprecated in 3.0 will remain supported in 3.0 until > 2026-09-07. If there is any further 3.x version designated as LTS, it > will give the lifetime of these APIs at least further five years. But > it wasn't decided yet whether there will be another 3.x version > designated as LTS. Thanks. That provides "rigidly defined areas of doubt and uncertainty". I have two observations: 1. Please ensure there is always an LTS release that is in support. (If necessary by extending support on the existing LTS.) 2. I would prefer to avoid declaring X.0 an LTS. If there are problems with the API in X.0, a new API can be added in X.1, to resolve it. -- Martin Bonner Any email and files/attachments transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.
