[DISCUSS] Introducing Apache Pulsar Office Hour Meetings
Dear Apache Pulsar Community, I hope you are doing well. As our community continues to grow, we want to ensure that everyone has the opportunity to actively participate and benefit from the collective knowledge and experience within the Apache Pulsar ecosystem. To achieve this, I discussed with some contributors, and we want to introduce a new initiative: Apache Pulsar Office Hour Meetings. What are Apache Pulsar Office Hour Meetings? Apache Pulsar Office Hour Meetings are informal gatherings where both developers and users can come together to discuss various aspects of Apache Pulsar. Unlike our traditional community meetings, which tend to be more developer-focused, these office hours are designed to cater to the broader community, including users, enthusiasts, and those who are just starting their journey with Apache Pulsar. Why Office Hours? We've noticed that our community meetings have primarily attracted developers, and we want to ensure that we address the needs and questions of our diverse user base. The office hour format allows for a more open and user-friendly discussion, allowing users to share their experiences, ask questions, and learn from one another. What to Expect? During these office hours, we encourage participants to bring their questions, share use cases, and discuss any challenges they might face with Apache Pulsar. We aim to foster a collaborative environment where seasoned users and newcomers feel comfortable engaging with the community. We believe that this format will help us bridge the gap between developers and users, creating a more inclusive and vibrant community. When? We plan to integrate Apache Pulsar Office Hour Meetings into our existing community meeting schedule. This way, we can maximise participation and ensure that everyone has the opportunity to join the conversation. The office hours will parallel the community meeting, allowing both groups to benefit from shared insights. Please leave your valuable comments and suggestions. Thanks! Sincerely, Mattison
Re: [VOTE] PIP-315: Configurable max delay limit for delayed delivery
+1 (non-binding) Thanks, Cong Zhao On 2023/11/15 03:59:46 Kevin Lu wrote: > Hi All, > > This thread is to start a vote for PIP-315. > > PIP: https://github.com/apache/pulsar/pull/21490 > Discussion thread: > https://lists.apache.org/thread/285nm08842or324rxc2zy83wxgqxtcjp > > Regards, > Kevin >
Re: [Discuss] Release Pulsar C++ Client 3.4.1
+1 Thanks for your fixes. BR, Zike Yang On Thu, Nov 16, 2023 at 5:48 PM Yunze Xu wrote: > > There is another critical issue introduced by 3.4.0: > https://github.com/apache/pulsar-client-python/issues/162 > > I will open another fix for it. > > Thanks, > Yunze > > On Thu, Nov 16, 2023 at 12:45 PM Yunze Xu wrote: > > > > In the latest C++ Client 3.4.0 release, we observed a regression > > https://github.com/apache/pulsar-client-cpp/issues/346. It's a > > critical bug that a crash could happen for each reconnection. > > > > I pushed a fix (https://github.com/apache/pulsar-client-cpp/pull/347). > > After it's merged, I will start the release process for 3.4.1. > > > > Please let me know if you have any questions. > > > > Thanks, > > Yunze
Re: [Discuss] Release Pulsar C++ Client 3.4.1
There is another critical issue introduced by 3.4.0: https://github.com/apache/pulsar-client-python/issues/162 I will open another fix for it. Thanks, Yunze On Thu, Nov 16, 2023 at 12:45 PM Yunze Xu wrote: > > In the latest C++ Client 3.4.0 release, we observed a regression > https://github.com/apache/pulsar-client-cpp/issues/346. It's a > critical bug that a crash could happen for each reconnection. > > I pushed a fix (https://github.com/apache/pulsar-client-cpp/pull/347). > After it's merged, I will start the release process for 3.4.1. > > Please let me know if you have any questions. > > Thanks, > Yunze
Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.0 Candidate 2
+1 (binding) - verified source package checksum and signature. - verified staged maven artifacts by running a test app built with Gradle. -Lari On 2023/11/15 09:14:58 Christophe Bornet wrote: > This is release candidate 2 for the Reactive Java client for Apache > Pulsar, version 0.5.0. > > *** Please download, test and vote on this release. This vote will > stay open for at least 72 hours *** > > Note that we are voting upon the source (tag). Binaries in the Maven > repository are provided for convenience. > > Source package: > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.0-candidate-2/ > > SHA-512 checksums: > 932a8942a1c6249d7cf85ee657633ebf2d38fac24aa5e5c5821ba99e665aa7e3ea785b1e2587688920fe8878a8f24318dc1aaa40ad5b3eb4b234a46425270660 > pulsar-client-reactive-0.5.0-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1246/ > > The tag to be voted upon: > v0.5.0-candidate-2 (b8294e41540d0932f7c9b235369e429fe5d44915) > https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.0-candidate-2 > > Please download the source package, and follow detailed instructions > for pulsar-client-reactive release validation at > https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation > . > > Best regards > > Christophe Bornet >