Personally I think we should create the first release as early as possible.
This would allow more people starting using the native go client. We can
take more feedback from people when they start using it. We can add a note
that the current release version is "developer preview" and warn people
that the API is subject to change in the future.

It is just my 2 cents.

Thanks,
Sijie

On Wed, Dec 18, 2019 at 11:33 AM xiaolong ran <ranxiaolong...@gmail.com>
wrote:

> Yes, agree with you. Maybe we can plan what features we need
> to implement in the first release. and accelerate the release
> process of pulsar-client-go.
>
> --
> Thanks
> Xiaolong Ran
>
>
> > 在 2019年12月18日,上午2:45,Matteo Merli <matteo.me...@gmail.com> 写道:
> >
> > There are still a number of critical pieces of the Go client library
> > that are being worked on.
> > Before these get settled we should avoid making a release that will
> > settle the API and the semantics.
> >
> >
> >
> >
> > --
> > Matteo Merli
> > <matteo.me...@gmail.com>
> >
> > On Tue, Dec 17, 2019 at 6:01 AM Guangning E <eguangn...@gmail.com>
> wrote:
> >>
> >> That sounds good to me, a stable version of native go client is
> important.
> >>
> >> Thanks,
> >> Guangning
> >>
> >> xiaolong ran <ranxiaolong...@gmail.com> 于2019年12月17日周二 下午9:15写道:
> >>
> >>> Hi all committers:
> >>>
> >>> Since the [pulsar-client-go](
> https://github.com/apache/pulsar-client-go <
> >>> https://github.com/apache/pulsar-client-go>) repo has
> >>> been transferred to the ASF under Pulsar PMC, I would suggest us
> creating
> >>> the
> >>> first pulsar-client-go apache release as soon as possible. So that we
> can
> >>> identify
> >>> what to release and what are the potential issues to fix to follow the
> >>> Apache way.
> >>>
> >>> This is the email thread for discussing the first pulsar-client-go
> release.
> >>> Please chime in with your thoughts.
> >>>
> >>>
> >>> --
> >>>
> >>> Best regarding,
> >>> Xiaolong Ran
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
>
>

Reply via email to