Thank you for your comments. I proposed the versioning rule of Node.js Client. Please review it if you have time. https://github.com/apache/pulsar-client-node/pull/287
Thanks, Yuto Yuto Furuta Yahoo Japan Corp. E-mail: yfur...@yahoo-corp.jp ________________________________ 差出人: Yunze Xu <y...@streamnative.io.INVALID> 送信日時: 2023年1月10日 16:19 宛先: dev@pulsar.apache.org <dev@pulsar.apache.org> 件名: Re: [DISCUSS] Should we bump up Node.js Client for C++ Client's upgrade My answer is yes. Some bug fixes might be included in a newer C++ client. But I think we don't need to start a release in a hurry once a newer C++ client is released. Thanks, Yunze On Tue, Jan 10, 2023 at 3:03 PM Zike Yang <z...@apache.org> wrote: > > Hi, Yuto Furuta, > > Currently, the latest Nodejs client 1.8.0 is already tied to the > latest C++ client 3.1.0. If there is a new C++ client version release, > I think it's also better to release a new Nodejs client version that > is tied to the latest C++ client version even though there are no new > commits in the Nodejs client. In this case, we can make sure the > latest Nodejs client always gets the latest updates or bug fixes of > the C++ client. > > BR, > Zike Yang > > On Tue, Jan 10, 2023 at 1:57 PM Yuto Furuta <yfur...@yahoo-corp.jp> wrote: > > > > Hi all, > > > > Currently Node.js Client is tied to specified version of C++ Client due to > > the following PR: > > https://github.com/apache/pulsar-client-node/pull/235 > > > > Should we bump up the version of Node.js Client even when there is no > > update except for C++ Client’s upgrade(at least for critical bug fixies)? > > > > > > Best Regards, > > Yuto > > > > Yuto Furuta > > Yahoo Japan Corp. > > E-mail: yfur...@yahoo-corp.jp
