flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From greghogan <...@git.apache.org>
Subject [GitHub] flink issue #5138: [FLINK-8217] [Kinesis connector] Properly annotate APIs o...
Date Tue, 12 Dec 2017 15:50:05 GMT
Github user greghogan commented on the issue:

    https://github.com/apache/flink/pull/5138
  
    @bowenli86 the `@Public` annotation is much more than an acknowledgement, it promises
that Flink will support that API essentially forever (despite the large number of "2.0" tickets,
it's likely that few APIs will be modified). If there is an implicit annotation I think it
is closer to `@Internal` than to `@PublicEvolving`, and either of these two can be used with
care without buy-in from the full developer community.
    
    I'm not sure that a FLIP is the best way to handle the promotion of `@PublicEvolving`
to `@Public`. I think this might be better handled once per release, and there are other "bulk"
considerations as well such as dependency versions which we may want to formalize in the release
schedule.


---

Mime
View raw message