If there are any planned API/ABI change on v19.02, deprecation notice patches
for them should be sent, approved and merged withing v18.11 scope which is only
a few days away.

If you will be working on a feature for v19.02, please take some time think if
it will cause any API/ABI change.
And if it will so, please send the deprecation notice for it ASAP, otherwise
your feature can be blocked for the release because of API/ABI breakage it 
causes.

Thanks,
ferruh

Reply via email to