Ivan, thanks, I agree, added this clause: The vote we are going to have is reduced to two choices so far: * Never deprecate the old APIs unless the new APIs are stable and released without @IgniteExperimental. The old APIs javadoc may be updated with a reference to new APIs to encourage users to evaluate new APIs. The deprecation and new API release may happen simultaneously if the new API is not marked with @IgniteExperimental or the annotation is removed in the same release. * Allow to deprecate the old APIs even when new APIs are marked with @IgniteExperimental to explicitly notify users that old APIs will be removed in the next major release AND new APIs are available Neither of cases prohibits deprecation of an API without a replacement if community decided so.
Are we good to go?
