Please validate and vote on the Apache Pulsar 5.0.0-M2 release candidate: • [VOTE] Release Apache Pulsar 5.0.0-M2 based on 5.0.0-M2-candidate-1 Since 5.0.0-M2 contains major changes, such as the switch to Gradle build it would be appreciated if the staging repository could be tested to validate that artifacts have been properly published and contain correct maven and gradle module metadata. staging repository: repository.apache.org/content/repositories/orgapachepulsar-1419 Please try out a Pulsar application by upgrading to 5.0.0-M2 version using the staging repository. It would be useful if existing Pulsar apps with maven and gradle builds would be tested. Please notice the new

pulsar-client-v5-all

and

pulsar-client-v5-shaded

modules documented currently at github.com/apache/pulsar/…/pulsar-client-v5-all. These dependencies include also the "v4 client" + admin client.

pulsar-client-v5-shaded

replaces

pulsar-client

,

pulsar-client-admin

and

pulsar-client-all

and

pulsar-client-v5-all

depends on unshaded

pulsar-client-original

and

pulsar-admin-original

. For v5 applications, it's recommended to use the default unshaded dependencies and handle possible dependency conflicts in the application. For example the usage of

netty-bom

is highly recommended to align Netty versions to latest 4.2.x release. Release validation instructions are at pulsar.apache.org/contribute/validate-release-candidate (documented validation hasn't been improved to cover v5 yet). To reduce the barrier for validation (mandated by ASF processes and our existing release process), there's also scripts available that you can use to run checks on your own hardware/vm within docker or directly as a bash script. @Tboy @Yunze Xu @Zixuan Liu @孟祥迎 @Entvex @Enrico Olivelli @Cong Zhao @Jason918 @Baodi Shi