> I think 2759 is merged after Joe started the release process. We can
> consider adding it to 2.2.1

@Sijie:Ok, Thanks.

Joe F <j...@apache.org> 于2018年10月12日周五 上午6:56写道:

> Given the issue identified, this vote is cancelled until
> https://github.com/apache/pulsar/issues/2778 is fixed
>
> Candidate-2 up will be put up for vote after this fix is completed
>
> Thank you
> Joe
>
> ---------- Forwarded message ---------
> From: Matteo Merli <mme...@apache.org>
> Date: Thu, Oct 11, 2018 at 3:30 PM
> Subject: Re: [VOTE] Pulsar Release 2.2.0 Candidate 1
> To: <dev@pulsar.apache.org>
>
>
> We have found there are some issues with Netty shading in master (that are
> also reflected in this candidate). This impacts all clients that have other
> Netty dependencies in the classpath.
>
> Working on a fix.
>
>
> Matteo
>
> On Wed, Oct 10, 2018 at 5:16 PM Joe F <j...@apache.org> wrote:
>
> > This is the first release candidate for Apache Pulsar, version  2.2.0
> >
> > It adds new features and also fixes for various issues from 2.1.1
> >
> >  * Pulsar Java Client Interceptors
> >  * Integration of functions and io with schema registry
> >  * Dead Letter Topic
> >  * Flink Source connector
> >  * JDBC Sink Connector
> >  * HDFS Sink Connector
> >  * Google Cloud Storage Offloader
> >  * Pulsar SQL
> >
> >
> > A complete list of enhancements and fixes can be viewed at
> > https://github.com/apache/pulsar/milestone/16?closed=1
> >
> >
> > *** 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
> > convenience.
> >
> > Source and binary files:
> >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.2.0-candidate-1/
> >
> > SHA-512 checksums:
> >
> >
> >
>
> 591abefd40ce20b1a1d76717c5322b749ce5254d982b653632ea8e06f99115f1a9f1772139e184f524dbd81d6d230c59b3a6032abcc6185b4d7b06b79a3592c2
> > ./apache-pulsar-2.2.0-bin.tar.gz
> >
> >
> >
>
> b35d4f6a1e5313c51b1d4caabc6e2d88ab30602b6b59436531c512c692b6f9dbb585d1f03a57761dae5b5ab045b3d3281bd49690e0a1a374b0a4ee01bfafac48
> > ./apache-pulsar-2.2.0-src.tar.gz
> >
> >
> >
>
> 7dcf6a94eb22785366c2b98cf98c1804b3828798e17d9700a438a41d3934a4f26f415c17003be1c4e664cce98d50f3dd937ccf927f98a5e0de10a3256cb1a4fc
> > ./apache-pulsar-io-connectors-2.2.0-bin.tar.gz
> >
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1029
> >
> > The tag to be voted upon:
> > v2.2.0-candidate-1 dd509298aad74f720089f675884196f0cf3
> > https://github.com/apache/pulsar/releases/tag/v2.2.0-candidate-1
> >
> > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > https://dist.apache.org/repos/dist/release/pulsar/KEYS
> >
> > Please download the the source package, and follow the README to build
> and
> > run the Pulsar standalone service.
> >
> > Here is a guide for validating a release candidate:
> > https://github.com/apache/pulsar/wiki/Release-Candidate-Validation
> > <
> >
>
> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation
> > >
> >
> >
> > Joe
> >
>

Reply via email to