[VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
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
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
+1 Allow, because once the community has made a decision to introduce new APIs instead of an old one - stabilization is just a matter of time. On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk wrote: > > 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 -- Best Regards, Vyacheslav D.
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit, We can't deprecate old API while a new API isn't stable. пн, 10 февр. 2020 г. в 11:14, Vyacheslav Daradur : > +1 Allow, because once the community has made a decision to introduce > new APIs instead of an old one - stabilization is just a matter of > time. > > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > wrote: > > > > 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 > > > > -- > Best Regards, Vyacheslav D. > -- BR, Sergey Antonov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit 1. As a library user I will stuck. Generally I do not want to use either experimental or deprecated APIs in my production code. I will not be able to upgrade. 2. We do not manage development resources in the Community. There cannot be a reliable guarantee that any experimental API will be finalized and stabilized. Best regards, Ivan Pavlukhin пн, 10 февр. 2020 г. в 11:20, Sergey Antonov : > > -1 Prohibit, We can't deprecate old API while a new API isn't stable. > > пн, 10 февр. 2020 г. в 11:14, Vyacheslav Daradur : > > > +1 Allow, because once the community has made a decision to introduce > > new APIs instead of an old one - stabilization is just a matter of > > time. > > > > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > > wrote: > > > > > > 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 > > > > > > > > -- > > Best Regards, Vyacheslav D. > > > > > -- > BR, Sergey Antonov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
*[-1 Prohibit]* Because it looks silly when old API is deprecated and new API is experimental and it can confuse users and developers. New API can be stabilized before the deprecation of old API. On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk wrote: > 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 >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
+1 10.02.2020, 11:02, "Alexey Goncharuk" : > 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
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit as PMC, I'd like new annotation, but suggest to play with them for the next 1-2 releases пн, 10 февр. 2020 г., 11:30 ткаленко кирилл : > +1 > > 10.02.2020, 11:02, "Alexey Goncharuk" : > > 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 >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit It looks inconsistent to me deprecate one API without present new stable API as replacement. пн, 10 февр. 2020 г. в 11:02, Alexey Goncharuk : > 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 > -- Живи с улыбкой! :D
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit. @deprecated annotation normally means that the method or class or whatever is not recommended to use, since a new proper implementation is available, and people should use it instead. But with @IgniteExperimental this is not the case. Denis On 10/02/2020, 11:45, "Юрий" wrote: -1 Prohibit It looks inconsistent to me deprecate one API without present new stable API as replacement. пн, 10 февр. 2020 г. в 11:02, Alexey Goncharuk : > 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 > -- Живи с улыбкой! :D
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit. We must not deprecate old API without have a new stable well-documented alternative and a way to migrate to new one. On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk wrote: > 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 > -- Best regards, Andrey V. Mashenkov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
+1 > 10 февр. 2020 г., в 11:57, Andrey Mashenkov > написал(а): > > -1 Prohibit. > > We must not deprecate old API without have a new stable well-documented > alternative and a way to migrate to new one. > > > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > wrote: > >> 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 >> > > > -- > Best regards, > Andrey V. Mashenkov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit because there is a non-zero chance that the new API will never be stabilized. -- Kind Regards Roman Kondakov On 10.02.2020 11:13, Vyacheslav Daradur wrote: > +1 Allow, because once the community has made a decision to introduce > new APIs instead of an old one - stabilization is just a matter of > time. > > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > wrote: >> >> 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 > > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit >From my point of view, deprecation of the existing API will confuse users in case API suggested as a replacement is marked with @IgniteExperimental. On Mon, Feb 10, 2020 at 12:20 PM Nikolay Izhikov wrote: > +1 > > > 10 февр. 2020 г., в 11:57, Andrey Mashenkov > написал(а): > > > > -1 Prohibit. > > > > We must not deprecate old API without have a new stable well-documented > > alternative and a way to migrate to new one. > > > > > > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > > > wrote: > > > >> 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 > >> > > > > > > -- > > Best regards, > > Andrey V. Mashenkov > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit because otherwise, instead of one stable API we'll have the old(not recommend to use) and unstable one. Which is not user-friendly. -- Best regards, Anton Kalashnikov 10.02.2020, 12:28, "Ivan Rakov" : > -1 Prohibit > > From my point of view, deprecation of the existing API will confuse users > in case API suggested as a replacement is marked with @IgniteExperimental. > > On Mon, Feb 10, 2020 at 12:20 PM Nikolay Izhikov > wrote: > >> +1 >> >> > 10 февр. 2020 г., в 11:57, Andrey Mashenkov >> написал(а): >> > >> > -1 Prohibit. >> > >> > We must not deprecate old API without have a new stable well-documented >> > alternative and a way to migrate to new one. >> > >> > >> > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > > >> > wrote: >> > >> >> 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 >> >> >> > >> > >> > -- >> > Best regards, >> > Andrey V. Mashenkov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1, sounds confusing, i wan`t use deprecated API and @IgniteExperimental it`s something unknown with undefined «time for support». >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 >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky wrote: > > -1, sounds confusing, i wan`t use deprecated API > and @IgniteExperimental it`s something unknown with undefined «time for > support». > > > > >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 > > > > > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn wrote: > -1 Prohibit > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > wrote: > > > > > -1, sounds confusing, i wan`t use deprecated API > > and @IgniteExperimental it`s something unknown with undefined «time for > > support». > > > > > > > > >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 > > > > > > > > > > > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit We should not deprecate old API unless the new one will be released as a stable version. Thanks, S. пн, 10 февр. 2020 г. в 13:19, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: > -1 Prohibit > > On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn > wrote: > > > -1 Prohibit > > > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > > wrote: > > > > > > > > -1, sounds confusing, i wan`t use deprecated API > > > and @IgniteExperimental it`s something unknown with undefined «time for > > > support». > > > > > > > > > > > > >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 > > > > > > > > > > > > > > > > > > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 because it's controversial to deprecation rules [1] [1] https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation.html пн, 10 февр. 2020 г. в 14:03, Вячеслав Коптилин : > -1 Prohibit > > We should not deprecate old API unless the new one will be released as a > stable version. > > Thanks, > S. > > > пн, 10 февр. 2020 г. в 13:19, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com>: > > > -1 Prohibit > > > > On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn > > wrote: > > > > > -1 Prohibit > > > > > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > > > wrote: > > > > > > > > > > > -1, sounds confusing, i wan`t use deprecated API > > > > and @IgniteExperimental it`s something unknown with undefined «time > for > > > > support». > > > > > > > > > > > > > > > > >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 > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best regards, Alexei Scherbakov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
Hello! +1 because it is possible that old API is obviously going away some time in the future, such as if it is inherently unsafe. I don't see why we should not indicate this fact as soon as it is known. Experimental API can implement partial or complete fix but not be stabilized yet. In fact, it is partial replacements that I'm worried about. Also, imagine we have some API already deprecated, and we want to add new experimental feature for the same purpose, at least partially. This means we either can't add it, can't mark as IgniteExperimental, or we have to un-deprecate old API, which is silly. Regards, -- Ilya Kasnacheev пн, 10 февр. 2020 г. в 15:34, Alexei Scherbakov < alexey.scherbak...@gmail.com>: > -1 because it's controversial to deprecation rules [1] > > [1] > > https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation.html > > > > пн, 10 февр. 2020 г. в 14:03, Вячеслав Коптилин >: > > > -1 Prohibit > > > > We should not deprecate old API unless the new one will be released as a > > stable version. > > > > Thanks, > > S. > > > > > > пн, 10 февр. 2020 г. в 13:19, Dmitriy Govorukhin < > > dmitriy.govoruk...@gmail.com>: > > > > > -1 Prohibit > > > > > > On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn > > > wrote: > > > > > > > -1 Prohibit > > > > > > > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > > > > wrote: > > > > > > > > > > > > > > -1, sounds confusing, i wan`t use deprecated API > > > > > and @IgniteExperimental it`s something unknown with undefined «time > > for > > > > > support». > > > > > > > > > > > > > > > > > > > > >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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Best regards, > Alexei Scherbakov >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
+1 I think we are talking about huge API reorganization, not a simple renaming [1]. [1] https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation.html On Mon, 10 Feb 2020 at 16:32, Ilya Kasnacheev wrote: > > Hello! > > +1 because it is possible that old API is obviously going away some time in > the future, such as if it is inherently unsafe. > > I don't see why we should not indicate this fact as soon as it is known. > > Experimental API can implement partial or complete fix but not be > stabilized yet. In fact, it is partial replacements that I'm worried about. > > Also, imagine we have some API already deprecated, and we want to add new > experimental feature for the same purpose, at least partially. > This means we either can't add it, can't mark as IgniteExperimental, or we > have to un-deprecate old API, which is silly. > > Regards, > -- > Ilya Kasnacheev > > > пн, 10 февр. 2020 г. в 15:34, Alexei Scherbakov < > alexey.scherbak...@gmail.com>: > > > -1 because it's controversial to deprecation rules [1] > > > > [1] > > > > https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation.html > > > > > > > > пн, 10 февр. 2020 г. в 14:03, Вячеслав Коптилин > >: > > > > > -1 Prohibit > > > > > > We should not deprecate old API unless the new one will be released as a > > > stable version. > > > > > > Thanks, > > > S. > > > > > > > > > пн, 10 февр. 2020 г. в 13:19, Dmitriy Govorukhin < > > > dmitriy.govoruk...@gmail.com>: > > > > > > > -1 Prohibit > > > > > > > > On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn > > > > wrote: > > > > > > > > > -1 Prohibit > > > > > > > > > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > > > > > wrote: > > > > > > > > > > > > > > > > > -1, sounds confusing, i wan`t use deprecated API > > > > > > and @IgniteExperimental it`s something unknown with undefined «time > > > for > > > > > > support». > > > > > > > > > > > > > > > > > > > > > > > > >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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Best regards, > > Alexei Scherbakov > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit We should not deprecate the old API if the new API could change in the near future.
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit >From my point of view, we should not deprecate the old API if the new API is marked as experemental. On Mon, Feb 10, 2020 at 4:47 PM Konstantin Orlov wrote: > -1 Prohibit > > We should not deprecate the old API if the new API could change in the > near future. > > -- Alexey Kuznetsov
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit On Mon, Feb 10, 2020 at 5:30 PM Alexey Kuznetsov wrote: > -1 Prohibit > > From my point of view, we should not deprecate the old API if the new API > is marked as experemental. > > > On Mon, Feb 10, 2020 at 4:47 PM Konstantin Orlov > wrote: > > > -1 Prohibit > > > > We should not deprecate the old API if the new API could change in the > > near future. > > > > > > -- > Alexey Kuznetsov >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
[-1 Prohibit] - Denis On Mon, Feb 10, 2020 at 12:02 AM Alexey Goncharuk wrote: > 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 >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit пн, 10 февр. 2020 г. в 20:54, Denis Magda : > [-1 Prohibit] > > - > Denis > > > On Mon, Feb 10, 2020 at 12:02 AM Alexey Goncharuk > wrote: > > > 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 > > >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk wrote: > > 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
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit. To me as a developer the situation when old but stable API is deprecated with only experimental (thus unstable/unfinished) alternative is very far from comfortable. And from outside folks it may look like as a sign of immature processes inside Ignite community (which is definitely not the case) and reduce overall users' impression. On Tue, Feb 11, 2020 at 2:20 PM Andrey Gura wrote: > -1 Prohibit > > On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk > wrote: > > > > 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 >
Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
-1 Prohibit: My justification builds solely on the possibility to encourage a user to switch to an API that will be changed and later break the compilation.
[RESULT][VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental
Dear Ignite community, The vote is now closed. The votes spread the following way: [+1 Allow]: 5 votes: Vyacheslav Daradur Tkalenko Kirill Nikolay Izhikov Ilya Kasnacheev Maxim Muzafarov [-1 Prohibit]: 23 votes: Sergey Antonov Ivan Pavlukhin Philipp Masharov Alexey Zinoviev Yuri Gerzhedovich Mekhanikov Denis Andrey Mashenkov Roman Kondakov Ivan Rakov Anton Kalashnikov Zhenya Stanilovsky Pavel Tupitsyn Dmitriy Govorukhin Vyacheslav Koptilin Alexei Scherbakov Konstantin Orlov Alexey Kuznetsov Anton Vinogradov Denis Magda Alex Plehanov Andrey Gura Sergey Chugunov Alexey Goncharuk Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Allow-or-prohibit-a-joint-use-of-deprecated-and-IgniteExperimental-td45749.html The Ignite community ruled in favor of prohibiting the simultaneous use of @deprecated and @IgniteExperimental. I will update the wiki shortly.
