Re: [ANNOUNCE] Apache Pulsar 2.3.0 released

Congratulations Matteo! One of the most exciting and polished release! On Fri, 22 Feb 2019 at 00:57, Matteo Merli wrote: > The Apache Pulsar team is proud to announce Apache Pulsar version 2.3.0. > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. It

Re: [ANNOUNCE] Apache Pulsar 2.3.0 released

Congratulations, Matteo! Thanks everyone for making this happen! Best Regards. Jia Zhai Beijing, China Mobile: 15810491983 On Fri, Feb 22, 2019 at 7:30 AM Sijie Guo wrote: > Congratulations, Matteo! Thanks everyone for making this happen! > > - Sijie > > On Fri, Feb 22, 2019 at 3:26 AM M

Re: [ANNOUNCE] Apache Pulsar 2.3.0 released

Congratulations, Matteo! Thanks everyone for making this happen! - Sijie On Fri, Feb 22, 2019 at 3:26 AM Matteo Merli wrote: > The Apache Pulsar team is proud to announce Apache Pulsar version 2.3.0. > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware

[ANNOUNCE] Apache Pulsar 2.3.0 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.3.0. 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 delivery of messages, automatic cursor management for subsc

Jenkins build is back to normal : pulsar-website-build #567

See

Build failed in Jenkins: pulsar-website-build #566

See -- [...truncated 1.19 MB...] create mode 100644 content/docs/ja/2.2.1/security-tls-authentication/index.html create mode 100644 content/docs/ja/2.2.1/security-tls-transport.html

Re: Major and Minor Release Management

On Thu, Feb 21, 2019 at 8:03 PM Ivan Kelly wrote: > > If so, I would suggest pulling the proposal out of the thread and do a > vote > > to make sure everyone in the community are on the same page. > > > > It is okay we don't have to document at this time. We can let you manage > > the process in

Build failed in Jenkins: pulsar-website-build #565

See Changes: [github] 2.3.0 release notes (#3637) -- [...truncated 1.15 MB...] Extracting: '/website/translated_docs/zh-CN/version-2.1.0-incubating/deploy-bare-metal.m

Build failed in Jenkins: pulsar-website-build #564

See -- [...truncated 1.38 MB...] Extracting: '/website/translated_docs/zh-CN/version-2.1.0-incubating/deploy-bare-metal.md' Extracting: '/website/translated_docs/zh-CN/version-2.1.0-

Re: Major and Minor Release Management

> If so, I would suggest pulling the proposal out of the thread and do a vote > to make sure everyone in the community are on the same page. > > It is okay we don't have to document at this time. We can let you manage > the process in next bugfix release. Once it is done, propagate the process > to

Build failed in Jenkins: pulsar-website-build #563

See Changes: [github] Added note on how to install `libpulsar` with brew on MacOS (#3641) [github] Fixed typo on the site build command line args (#3642) -- [...trunca

Slack digest for #dev - 2019-02-21

2019-02-20 17:46:33 UTC - Grant Wu: I have a really stupid question: how do I install `apt-install` command? 2019-02-20 17:47:32 UTC - Grant Wu: From here 2019-02-20 17:54:44 UTC - Guy Feldman: it should be just `apt install`

Re: Major and Minor Release Management

On Thu, Feb 21, 2019 at 4:53 PM Ivan Kelly wrote: > > Your proposal works for me. > > If it helps, I can volunteer to do the next bugfix release also. > +1 from me. If so, I would suggest pulling the proposal out of the thread and do a vote to make sure everyone in the community are on the same

Re: Major and Minor Release Management

> Your proposal works for me. If it helps, I can volunteer to do the next bugfix release also. -Ivan

Re: Major and Minor Release Management

On Thu, Feb 21, 2019 at 4:45 PM Ivan Kelly wrote: > > When it comes to release a minor release, he should : > > > > 1) go through all the issues in current master and pick the issues that > are > > required to cherry-pick to branches, and label them with `cherry-pick` > > label. > > 2) go through

Re: Major and Minor Release Management

> When it comes to release a minor release, he should : > > 1) go through all the issues in current master and pick the issues that are > required to cherry-pick to branches, and label them with `cherry-pick` > label. > 2) go through all the issues label with `cherry-pick` label, and > cherry-pick

Build failed in Jenkins: pulsar-website-build #562

See Changes: [github] Added link to get individual connectors on download page (#3635) -- [...truncated 954.43 KB...] [INFO] Pulsar IO :: Hbase