Dear Apache Ignite community, We would like to conduct a formal vote on the subject of whether to allow or prohibit a joint existence of @deprecated annotation for an old API and @IgniteExperimental [1] for a new (replacement) API. The result of this vote will be formalized as an Apache Ignite development rule to be used in future.
The discussion thread where you can address all non-vote messages is [2]. The votes are: *[+1 Allow]* Allow to deprecate the old APIs even when new APIs are marked with @IgniteExperimental to explicitly notify users that an old APIs will be removed in the next major release AND new APIs are available. *[-1 Prohibit]* 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. Neither of the choices prohibits deprecation of an API without a replacement if community decides so. The vote will hold for 72 hours and will end on February 13th 2020 08:00 UTC: https://www.timeanddate.com/countdown/to?year=2020&month=2&day=13&hour=8&min=0&sec=0&p0=utc-1 All votes count, there is no binding/non-binding status for this. [1] https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/lang/IgniteExperimental.java [2] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Public-API-deprecation-rules-td45647.html Thanks, --AG
