I also like the idea
+1
There was a discussion about tagging public API classes and methods, to
make it very clear what APIs should be stable across versions and what
might change.
Can we solve these things together:
public class ApiVisibility {
public static @interface Public {};
public static @interface PublicBeta {};
public static @interface Internal{};
private ApiVisibility () {}
}
@ApiVisibility.Public
public class SomeApiClass {
}
@ApiVisibility.PublicBeta
public class EvolvingClass {
}
@ApiVisibility.Internal
public class RuntimeClass {
}
Names are subject to debate ;-)
On Sun, Mar 29, 2015 at 5:04 PM, Chiwan Park <chiwanp...@icloud.com> wrote:
> +1
>
> Good idea. Users can accept API changes of “flink-staging” module with
> “Beta" badge.
>
> Regards.
> Chiwan Park (Sent with iPhone)
>
>
> > On Mar 29, 2015, at 11:38 PM, Robert Metzger <rmetz...@apache.org>
> wrote:
> >
> > Hi,
> >
> > In an offline discussion with other Flink committers, we came up with the
> > idea to mark new components from the "flink-staging" module with a "Beta"
> > badge in the documentation.
> > This way, we make it very clear that the component is still under heavy
> > development.
> >
> > If we agree on this, I'll file a JIRA and add the badge to the
> > documentation.
> >
> >
> > Best,
> > Robert
>
>
