With regards to the annotations, I think we should expect that we'll always
have some @Evolving APIs. Even though much of the platform is mature, we'll
continue to improve and extend it. I'm generally not a fan of @Unstable
(since there's rarely a reason to make breaking changes in bug fix release)
and I would not mind if we removed them from the codebase for good.

Ismael

On Tue, Jul 18, 2017 at 4:07 PM, Guozhang Wang <wangg...@gmail.com> wrote:

> Currently the only @unstable annotations left are on Streams and one class
> of Security modules, and I think we have a good chance of removing them all
> in the next release.
>
> We also have a few @evolving annotations on the Admin, Streams, Security
> modules etc. And I think we can try to also eliminate as many of them as
> possible if people feel confident about these APIs but maybe a stretch goal
> to get rid of all of them.
>
> Guozhang
>
> On Tue, Jul 18, 2017 at 3:49 PM, Gwen Shapira <g...@confluent.io> wrote:
>
> > Also fine with the change in general.
> >
> > As you mentioned, 1.x indicates mature APIs, compatibility and stability.
> > Are we going to remove the @unstable annotations in this release?
> >
> > Gwen
> >
> > On Tue, Jul 18, 2017 at 3:43 PM Ismael Juma <ism...@juma.me.uk> wrote:
> >
> > > Hi Guozhang,
> > >
> > > Thanks for volunteering to be the release manager for the next release!
> > >
> > > I am +1 on naming the next release 1.0.0. As you said, Kafka is mature
> > > enough and this will make it easier for others to understand our
> > versioning
> > > policy.
> > >
> > > A couple of minor questions inline.
> > >
> > > On Tue, Jul 18, 2017 at 3:36 PM, Guozhang Wang <wangg...@gmail.com>
> > wrote:
> > >
> > > > major.minor.bugfix[.release-candidate]
> > > >
> > >
> > > I think you mean major.minor.bugfix-rc (i.e. we typically use a dash
> > > instead of dot for the RCx qualifier).
> > >
> > > >
> > > > How do people feel about 1.0.0.x as the next Kafka version?
> > >
> > >
> > > Do you mean 1.0.0?
> > >
> > > Ismael
> > >
> >
>
>
>
> --
> -- Guozhang
>

Reply via email to