This message was deleted.
# general
s
This message was deleted.
c
Hi @Alexander Preuß Excellent topic - thankyou I don’t think there is anything ongoing or a plan yet to bump up to 3.0.0 client. In spring-pulsar we use the pulsar client 3.0.0 and pulsar reactive client 0.3.0 (which in turn uses pulsar client 2.11.0). Same story goes for Project Reactor. In spring-pulsar we use the reactor 3.6.0 (whereas the pulsar reactive client uses 3.5.4). I plan on testing the above scenarios (using updated libs in spring-pulsar but using current reactive client that uses the older versions of the libs). I am in favor of upgrading both of these libs but this is also a major (
2.x->3.x
) bump for Pulsar Client and a minor (
3.5.4->3.6.0
) bump for Reactor. The current versioning has been
0.2.x
and
0.3.x
. Should we upgrade reactor and move version to
0.4.x
and update Pulsar Client and move it to
1.0.0
? Or should we make the updates and move it to
1.0.0
? @Christophe Bornet @Lari Hotari wdyt?
👍 1
c
Yes. Let's upgrade the reactive client to 3.0.0
c
Any concerns of updating reactor to 3.6.0 (once it is avaliable)?
l
Yes, let's make it 3.0.0 . No concerns about updating reactor to 3.6.0. I'll be offline for at least next week while on vacation.
c
Nice. I can the PRs queued up (was planning on doing the Pulsar client sometime today). Then I will follow on w/ the Reactor one.