incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sijie Guo <>
Subject [VOTE] Pulsar Release 2.1.0-incubating Candidate 5
Date Wed, 25 Jul 2018 18:17:31 GMT
This is the 5th release candidate for Apache Pulsar, version

Link to the vote on dev@pulsar list:

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware.
It provides simple pub-sub semantics over topics, guaranteed at-least-once
and effective-once delivery of messages, automatic cursor management for
subscribers, and geo-replication.

This is a feature release, introducing following new features:

- Pulsar I/O: a serverless connector framework built on top of Pulsar
- TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3).
- Stateful Function: Pulsar Functions supports storing state back to
- Go Client: a Go client wrapping over existing cpp client.
- Avro and Protobuf schema are supported.

Full list of changes and fixes are available:

*** 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 are provided for

Source and binary files:

SHA-1 checksums:




Maven staging repo:

The tag to be voted upon:
v2.1.0-incubating-candidate-5 (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177)

Pulsar's KEYS file containing PGP keys we use to sign the release:

Please download the the source package, and follow the README to build
and run the Pulsar standalone service.

A few notes for voting 2.1.0 release:

- For compiling source distribution, use "mvn clean install
- Starting from this release, Pulsar is shipping RPM & DEB packages for
pulsar non-java clients.
- Starting from this release, Pulsar is shipping a binary distribution
called `apache-pulsar-io-connectors`
  including all built-in connectors. Each connector is packaged with all
their dependencies and
  a META-INF/DEPEDENCIES file with licensing information for
all dependencies.
- Since there are a lot of features introduced in 2.1, You can use the
instructions documented in the link for
  validating the binary release candidate:

- Sijie

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message