Re: [DISCUSS] Graduate Apache Pulsar (incubating) as a TLP
> We will make sure we clean up creator language. Just following up here: the change was already made yesterday ( https://github.com/apache/incubator-pulsar/pull/2557). The website is not yet updated because of unrelated issues in the website Jenkins job. Hopefully it will be fixed in next few hours. > Sounds fine to me. They just copied something that a TLP project probably shouldn’t be doing. It not the first time that has happened with that project. Regarding affiliations for committers, I would say that it's not that we have "copied" from the only TLP that had it in their "Team" page. I just did a spot check and it seems to be a quite common practice across the board. Few examples (taken ramdomly): http://hive.apache.org/people.html http://storm.apache.org/contribute/People.html http://activemq.apache.org/team.html http://camel.apache.org/team.html http://zookeeper.apache.org/credits.html http://avro.apache.org/credits.html On Tue, Sep 11, 2018 at 11:38 PM Dave Fisher wrote: > Hi Justin, > > Sent from my iPhone > > > On Sep 11, 2018, at 2:22 PM, Justin Mclean > wrote: > > > > Hi, > > > >>> I'm curious to why organisations are mention on the team page [2] > >> > >> I think we've followed what other projects are doing. e.g. > >> https://spark.apache.org/committers.html > >> > >> Any ASF policy on this that we can follow? > > > > Well projects should be independent [1] and lists who works for who may > make some question that, Who you work for should have no relevance on an > Apache project and I would not expect it to be listed on a team page. > > I think that this is debatable. I’d love to discuss it. In the case of > Pulsar it has been important in showing independence. Mentors and even > Sally have worked through a couple of situations in the podling. She has > offered to help out with a graduation announcement. We will make sure we > clean up creator language. > > > > > Re actually policy on this then yes [2] and in particular [3] Note: > > "Should not include corporate affiliations of actual contributors. > Committers are expected to participate in Apache projects as individuals, > and not as representatives of any employers. Including corporate > affiliations on pages that are primarily about the community of individuals > on a project can give the wrong impression to new community members about > the fact that projects are managed by PMCs of individuals, and not managed > by outside organizations." > > We will cleanup this page on graduation. > > I’ll start the VOTE in the morning. > > Regards, > Dave > > > > > Thanks, > > Justin > > > > 1. http://community.apache.org/projectIndependence.html > > 2. https://www.apache.org/foundation/marks/linking > > 3. https://www.apache.org/foundation/marks/linking#whoweare > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1
Created https://github.com/apache/incubator-pulsar/pull/2563 to ensure the release script doesn't generate the sha1 checksums anymore. On Tue, Sep 11, 2018 at 9:58 PM Jerry Peng wrote: > Thanks Dave for pointing that out. I have removed the SHA-1 checksums for > DEB and RPMS packages > > On Tue, Sep 11, 2018 at 6:48 PM Dave Fisher wrote: > > > Hi Jerry, > > > > Do we need SHA-1 for the DEB and RPMS packages? > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Sep 11, 2018, at 4:55 PM, Jerry Peng > > wrote: > > > > > > Thanks Henk for pointing that out. I have removed the SHA-1 checksums. > > > > > > Best, > > > > > > Jerry > > > > > >> On Tue, Sep 11, 2018 at 4:35 PM Henk P. Penning > wrote: > > >> > > >>> On Wed, 12 Sep 2018, Jerry Peng wrote: > > >>> > > >>> Date: Wed, 12 Sep 2018 00:31:35 +0200 > > >>> From: Jerry Peng > > >>> To: gene...@incubator.apache.org > > >>> Cc: dev@pulsar.incubator.apache.org > > >>> Subject: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1 > > >>> > > >>> This is the first release candidate for Apache Pulsar, version > > >>> 2.1.1-incubating. > > >> > > >>> Source and binary files: > > >>> > > >> > > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.1-incubating-candidate-1/ > > >> > > >>> SHA-1 checksums: > > >> > > >> Hi, > > >> > > >> SHA-1 checksum files shouldn't be publish checksums anymore. > > >> > > >> https://www.apache.org/dev/release-distribution#sigs-and-sums > > >> > > >> Please remove ; the vote may continue. > > >> > > >> Thanks ; regards, > > >> > > >> Henk Penning > > >> > > >> _ > > >> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_ > > >> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ > > >> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ > > >> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ > > >> > > >>> 506c172b13c1581f9b52769a4c6594541628b928 > > >>> apache-pulsar-2.1.1-incubating-bin.tar.gz > > >>> de3a74449a78d0713998544237dde59765ee121f > > >>> apache-pulsar-2.1.1-incubating-src.tar.gz > > >>> 1d38554e58cfd733fc2d54ec1442747daeb8fc1b > > >>> apache-pulsar-io-connectors-2.1.1-incubating-bin.tar.gz > > >>> > > >>> Maven staging repo: > > >>> > > https://repository.apache.org/content/repositories/orgapachepulsar-1026 > > >>> > > >>> The tag to be voted upon: > > >>> v2.1.1-incubating-candidate-1 > 68faf85083025b29bb6ab39028a1d467bd3d5217 > > >>> > > >> > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.1.1-incubating-candidate-1 > > >>> > > >>> Pulsar's KEYS file containing PGP keys we use to sign the release: > > >>> https://dist.apache.org/repos/dist/release/incubator/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/incubator-pulsar/wiki/Release-Candidate-Validation > > >>> > > >> > > > > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1
+1 Environment: MacOS 10.13 Checked: * Signatures * Bin distribution: - NOTICE, README, LICENSE - Start standalone service and producer/consumer test * Src distribution: - NOTICE, README, LICENSE - Compile and unit tests - RAT check - Start standalone service * Checked staging maven repository artifacts Matteo On Thu, Sep 6, 2018 at 8:48 PM Jerry Peng wrote: > Sorry there was a typo in my previous email: > > "v2.2.1-incubating-candidate-1" => "v2.1.1-incubating-candidate-1" > > On Thu, Sep 6, 2018 at 5:31 PM Jerry Peng > wrote: > > > This is the first release candidate for Apache Pulsar, version > > 2.1.1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/17?closed=1 > > > > Mostly bug fixes for 2.1.0 > > > > *** 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/incubator/pulsar/pulsar-2.1.1-incubating-candidate-1/ > > > > SHA-1 checksums: > > > > 506c172b13c1581f9b52769a4c6594541628b928 > > apache-pulsar-2.1.1-incubating-bin.tar.gz > > de3a74449a78d0713998544237dde59765ee121f > > apache-pulsar-2.1.1-incubating-src.tar.gz > > 1d38554e58cfd733fc2d54ec1442747daeb8fc1b > > apache-pulsar-io-connectors-2.1.1-incubating-bin.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1026 > > > > The tag to be voted upon: > > v2.2.1-incubating-candidate-1 68faf85083025b29bb6ab39028a1d467bd3d5217 > > > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.1.1-incubating-candidate-1 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/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/incubator-pulsar/wiki/Release-Candidate-Validation > > > -- Matteo Merli
[RESULT] [VOTE] Graduation resolution proposal
The vote is now closed with 13 binding and 2 non binding +1s. +1s Binding: * Matteo Merli * Sijie Guo * Joe Francis * Sanjeev Kulkarni * Dave Fisher * Rajan Dhabalia * P. Taylor Goetz * Jai Asher * Nozomi Kurihara * Hiroyuki Sakai * Ivan Kelly * Masahiro Sakamoto * Sahaya Andrews +1s Non binding: * Ali Ahmed * David Kjerrumgaard Thank you all for voting. Dave, please start the vote on the Incubator list. Thank you, Matteo On Mon, Sep 10, 2018 at 4:38 PM Sahaya Andrews wrote: > +1 > On Mon, Sep 10, 2018 at 3:14 AM Masahiro Sakamoto > wrote: > > > > +1 > > > > -- > > Masahiro Sakamoto > > Yahoo Japan Corp. > > E-mail: massa...@yahoo-corp.jp > > -- > > > > > -Original Message- > > > From: Matteo Merli [mailto:mme...@apache.org] > > > Sent: Saturday, September 08, 2018 9:22 AM > > > To: dev@pulsar.incubator.apache.org > > > Subject: [VOTE] Graduation resolution proposal > > > > > > Please vote on the proposal for Pulsar graduation to TLP to submit to > the > > > Incubator PMC. > > > > > > This vote will stay open for at least 72 hours. > > > > > > > > > > > > > > > Establish the Apache Pulsar Project > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > the Foundation and consistent with the Foundation's purpose to > establish > > > a Project Management Committee charged with the creation and > maintenance > > > of open-source software, for distribution at no charge to the public, > > > related to a highly scalable, low latency messaging platform running on > > > commodity hardware. It provides simple pub-sub and queue semantics over > > > topics, lightweight compute framework, automatic cursor management for > > > subscribers, and cross-datacenter replication. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), > > > to be known as the "Apache Pulsar Project", be and hereby is > established > > > pursuant to Bylaws of the Foundation; and be it further > > > > > > RESOLVED, that the Apache Pulsar Project be and hereby is responsible > for > > > the creation and maintenance of software related to a highly scalable, > low > > > latency messaging platform running on commodity hardware. > > > It provides simple pub-sub and queue semantics over topics, lightweight > > > compute framework, automatic cursor management for subscribers, and > > > cross-datacenter replication; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache Pulsar" be and > hereby > > > is created, the person holding such office to serve at the direction of > > > the Board of Directors as the chair of the Apache Pulsar Project, and > to > > > have primary responsibility for management of the projects within the > scope > > > of responsibility of the Apache Pulsar Project; and be it further > > > > > > RESOLVED, that the persons listed immediately below be and hereby are > > > appointed to serve as the initial members of the Apache Pulsar Project: > > > > > > * Boyang Jerry Peng > > > * Brad McMillen > > > * David Fisher > > > * Francis Christopher Liu > > > * Hiroyuki Sakai > > > * Ivan Brendan Kelly > > > * Jai Asher > > > * Jia Zhai > > > * Jim Jagielski > > > * Joe Francis > > > * Ludwig Pummer > > > * Masahiro Sakamoto > > > * Masakazu Kitajo > > > * Matteo Merli > > > * Nozomi Kurihara > > > * P. Taylor Goetz > > > * Rajan Dhabalia > > > * Sahaya Andrews > > > * Sanjeev Kulkarni > > > * Sebastián Schepens > > > * Siddharth Boobna > > > * Sijie Guo > > > * Yuki Shiga > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed > to > > > the office of Vice President, Apache Pulsar, to serve in accordance > with > > > and subject to the direction of the Board of Directors and the Bylaws > of > > > the Foundation until death, resignation, retirement, removal or > > > disqualification, or until a successor is appointed; and be it further > > > > > > RESOLVED, that the Apache Pulsar Project be and hereby is tasked with > the > > > migration and rationalization of the Apache Incubator Pulsar podling; > and > > > be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > Pulsar podling encumbered upon the Apache Incubator PMC are hereafter > > > discharged. > > > > > > > > > > > > > > > > > > -- > > > Matteo Merli > > > > -- Matteo Merli
[VOTE] Graduation resolution proposal
Please vote on the proposal for Pulsar graduation to TLP to submit to the Incubator PMC. This vote will stay open for at least 72 hours. Establish the Apache Pulsar Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub and queue semantics over topics, lightweight compute framework, automatic cursor management for subscribers, and cross-datacenter replication. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Pulsar Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Pulsar Project be and hereby is responsible for the creation and maintenance of software related to a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub and queue semantics over topics, lightweight compute framework, automatic cursor management for subscribers, and cross-datacenter replication; and be it further RESOLVED, that the office of "Vice President, Apache Pulsar" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Pulsar Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Pulsar Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Pulsar Project: * Boyang Jerry Peng * Brad McMillen * David Fisher * Francis Christopher Liu * Hiroyuki Sakai * Ivan Brendan Kelly * Jai Asher * Jia Zhai * Jim Jagielski * Joe Francis * Ludwig Pummer * Masahiro Sakamoto * Masakazu Kitajo * Matteo Merli * Nozomi Kurihara * P. Taylor Goetz * Rajan Dhabalia * Sahaya Andrews * Sanjeev Kulkarni * Sebastián Schepens * Siddharth Boobna * Sijie Guo * Yuki Shiga NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed to the office of Vice President, Apache Pulsar, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Pulsar Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Pulsar podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Pulsar podling encumbered upon the Apache Incubator PMC are hereafter discharged. -------- -- Matteo Merli
Re: [DRAFT] [UPDATED] Graduation resolution proposal
Thanks Taylor. I'll start the formal VOTE with the final version of draft. Matteo On Fri, Sep 7, 2018 at 4:57 PM P. Taylor Goetz wrote: > Thanks for your patience. I missed that there was a mentor question in > this thread. My apologies for that. > > You should hold a formal VOTE thread, and upon conclusion, start an IPMC > VOTE with a reference to the PPMC VOTE thread. > > Feel free to ask if you have more questions. > > -Taylor > > > On Sep 7, 2018, at 7:39 PM, Sijie Guo wrote: > > > > Mentors, what are the next steps for this? > > > >> On Wed, Sep 5, 2018 at 7:39 PM Matteo Merli wrote: > >> > >> Dave / mentors, > >> > >> since this thread was not marked with [VOTE], would we need to have a > >> separate vote thread or do you believe this one is enough to proceed? > >> > >> > >> Thanks, > >> Matteo > >> > >>> On Tue, Sep 4, 2018 at 12:56 AM Jia Zhai wrote: > >>> > >>> +1. > >>> > >>> I am honored to be asked to be on the PMC. Please keep me on the list. > ：） > >>> > >>> On Tue, Sep 4, 2018 at 2:47 PM Hiroyuki Sakai > >>> wrote: > >>> > >>>> +1 > >>>> > >>>> I would like to be part of PMC. > >>>> > >>>> Hiroyuki > >>>> > >>>> > >>>> -Original Message- > >>>> From: Masahiro Sakamoto > >>>> Reply-To: "dev@pulsar.incubator.apache.org" < > >>>> dev@pulsar.incubator.apache.org> > >>>> Date: Tuesday, September 4, 2018 15:43 > >>>> To: "dev@pulsar.incubator.apache.org" < > dev@pulsar.incubator.apache.org > >>> > >>>> Subject: RE: [DRAFT] [UPDATED] Graduation resolution proposal > >>>> > >>>>+1 > >>>> > >>>>I would like to be part of PMC. > >>>> > >>>>-- > >>>>Masahiro Sakamoto > >>>>Yahoo Japan Corp. > >>>>E-mail: massa...@yahoo-corp.jp > >>>>-- > >>>> > >>>>> -Original Message- > >>>>> From: Nozomi Kurihara [mailto:nkuri...@yahoo-corp.jp] > >>>>> Sent: Tuesday, September 04, 2018 2:27 PM > >>>>> To: dev@pulsar.incubator.apache.org > >>>>> Subject: RE: [DRAFT] [UPDATED] Graduation resolution proposal > >>>>> > >>>>> +1 > >>>>> > >>>>> And would like to be part of PMC. > >>>>> > >>>>> > >>>>> Nozomi > >>>>> > >>>>> > >>>>> 差出人: Ivan Kelly > >>>>> 送信日時: 2018年9月3日 16:38:41 > >>>>> 宛先: dev@pulsar.incubator.apache.org > >>>>> 件名: Re: [DRAFT] [UPDATED] Graduation resolution proposal > >>>>> > >>>>> +1 > >>>>> > >>>>> I wish to remain part of PMC. > >>>>> > >>>>> Regarding BookKeeper bylaws, BookKeeper has them because > >> ZooKeeper > >>>> had them > >>>>> when we branched off, and my understanding is that zookeeper had > >>>> them, > >>>>> because hadoop had them when they branched off. As far as I'm > >>>> concerned, > >>>>> they're unnecessary given the default asf bylaws, but that's a > >>>> discussion > >>>>> for another list. > >>>>> > >>>>> -Ivan > >>>>> > >>>>> On Sun, Sep 2, 2018 at 10:36 PM, P. Taylor Goetz < > >>> ptgo...@gmail.com> > >>>> wrote: > >>>>>> +1 > >>>>>> > >>>>>> -Taylor > >>>>>> > >>>>>>> On Sep 2, 2018, at 3:18 PM, Matteo Merli > >>>> wrote: > >>>>>>> > >>>>>>> Updated the initial draft by removing paragraph on the "have a > >>>>>>> tasking for creating set of bylaws". > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Establish the Apache Pulsar Project > >>>>>>> > >>>>>>>
Re: [DRAFT] [UPDATED] Graduation resolution proposal
Dave / mentors, since this thread was not marked with [VOTE], would we need to have a separate vote thread or do you believe this one is enough to proceed? Thanks, Matteo On Tue, Sep 4, 2018 at 12:56 AM Jia Zhai wrote: > +1. > > I am honored to be asked to be on the PMC. Please keep me on the list. ：） > > On Tue, Sep 4, 2018 at 2:47 PM Hiroyuki Sakai > wrote: > > > +1 > > > > I would like to be part of PMC. > > > > Hiroyuki > > > > > > -Original Message- > > From: Masahiro Sakamoto > > Reply-To: "dev@pulsar.incubator.apache.org" < > > dev@pulsar.incubator.apache.org> > > Date: Tuesday, September 4, 2018 15:43 > > To: "dev@pulsar.incubator.apache.org" > > Subject: RE: [DRAFT] [UPDATED] Graduation resolution proposal > > > > +1 > > > > I would like to be part of PMC. > > > > -- > > Masahiro Sakamoto > > Yahoo Japan Corp. > > E-mail: massa...@yahoo-corp.jp > > -- > > > > > -Original Message- > > > From: Nozomi Kurihara [mailto:nkuri...@yahoo-corp.jp] > > > Sent: Tuesday, September 04, 2018 2:27 PM > > > To: dev@pulsar.incubator.apache.org > > > Subject: RE: [DRAFT] [UPDATED] Graduation resolution proposal > > > > > > +1 > > > > > > And would like to be part of PMC. > > > > > > > > > Nozomi > > > > > > > > > 差出人: Ivan Kelly > > > 送信日時: 2018年9月3日 16:38:41 > > > 宛先: dev@pulsar.incubator.apache.org > > > 件名: Re: [DRAFT] [UPDATED] Graduation resolution proposal > > > > > > +1 > > > > > > I wish to remain part of PMC. > > > > > > Regarding BookKeeper bylaws, BookKeeper has them because ZooKeeper > > had them > > > when we branched off, and my understanding is that zookeeper had > > them, > > > because hadoop had them when they branched off. As far as I'm > > concerned, > > > they're unnecessary given the default asf bylaws, but that's a > > discussion > > > for another list. > > > > > > -Ivan > > > > > > On Sun, Sep 2, 2018 at 10:36 PM, P. Taylor Goetz < > ptgo...@gmail.com> > > wrote: > > > > +1 > > > > > > > > -Taylor > > > > > > > >> On Sep 2, 2018, at 3:18 PM, Matteo Merli > > wrote: > > > >> > > > >> Updated the initial draft by removing paragraph on the "have a > > > >> tasking for creating set of bylaws". > > > >> > > > >> > > > >> > > > >> Establish the Apache Pulsar Project > > > >> > > > >> WHEREAS, the Board of Directors deems it to be in the best > > interests > > > >> of the Foundation and consistent with the Foundation's purpose > to > > > >> establish a Project Management Committee charged with the > creation > > > >> and maintenance of open-source software, for distribution at no > > > >> charge to the public, related to a highly scalable, low latency > > > >> messaging platform running on commodity hardware. It provides > > simple > > > >> pub-sub and queue semantics over topics, lightweight compute > > > >> framework, automatic cursor management for subscribers, and > > > cross-datacenter replication. > > > >> > > > >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee > > > >> (PMC), to be known as the "Apache Pulsar Project", be and hereby > > is > > > >> established pursuant to Bylaws of the Foundation; and be it > > further > > > >> > > > >> RESOLVED, that the Apache Pulsar Project be and hereby is > > responsible > > > >> for the creation and maintenance of software related to a highly > > > >> scalable, low latency messaging platform running on commodity > > hardware. > > > >> It provides simple pub-sub and queue semantics over topics, > > > >> lightweight compute framework, automatic cursor management for > > &
[DRAFT] Podling report
Sorry for sending out at very last minute (deadline is today). Please take a look. I have added a paragraph regarding the branding discussion that happen in early June (as discussed with Taylor then) since the previous draft was already out at that point. --- Pulsar 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 subscribers, and cross-datacenter replication. Pulsar has been incubating since 2017-06-01. Most important issues to address in the move towards graduation: None Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? Earlier in June there have been few discussions on the private list regarding communications regarding Pulsar that were not coming from PPMC or that were not respecting the ASF policies. Clarifications followed between PPMC members, mentors and interested parties to ensure the mistakes were made in good faith and, in particular, to make sure everyone was fully has full understanding of ASF policies. There was no other branding related issue after the first occourence. How has the community developed since the last report? The community added 8 new contributors that submitted pull-requests which were merged into master. The number of users approaching the team on the Slack channel has kept steadily increasing since the last report. Many users have actively deployed. Pulsar for evaluation and production use cases. Different meetups were organized by project members and hosted by Yahoo in Sunnyvale and Yahoo Japan in Tokyo. We have presented Pulsar's introductions, updates on the state of the projects, deep-dives and hands-on tutorial, including recorded podcasts. One talk on Pulsar was presented at one at OSCon in July and there are several scheduled talks: 2 at ApacheCon in September, and 2 others at Strata New York in September. Since the last report the number of weekly-active-users on the Slack channel has increased from 53 to 88. How has the project developed since the last report? 28 authors have pushed 494 commits to master in the last 3 months. The project has made the its seventh release since joining the Apache Incubator (2.1.0-incubating on Aug 2nd). This release introduced these new features: * Pulsar IO: A connector framework for moving data in and out of Apache Pulsar leveraging Pulsar Functions runtime. * A number of builtin connectors: (Aerospike, Cassandra, Kafka, Kinesis, RabbitMQ, Twitter) * Tiered Storage: An extension in Pulsar segment store to offload older segments into long term storage (e.g. HDFS, S3). S3 support is supported in 2.1 release. * Stateful function: Pulsar Functions is able to use State API for storing state within Pulsar. * Pulsar Go Client * Avro and Protobuf Schema support Community is actively working on a bug-fix release (2.1.1-incubating) and on the next milestone, 2.2 release for which the biggest feature will be support for SQL within Pulsar. Since June, 5 new PIPs (Pulsar Improvement Proposals) for major feature/changes, have been submitted to the wiki and discussed in the mailing list. PIP 23: Message Tracing By Interceptors PIP 22: Pulsar Dead Letter Topic PIP 21: Pulsar Edge Component PIP 20: Mechanism to revoke TLS authentication PIP 19: Pulsar SQL How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2018-08-02, 2.1.0-incubating When were the last committers or PPMC members elected? 2018-06-11 - Ivan Kelly 2018-06-11 - Jia Zhai -- Matteo Merli
Re: [DRAFT] [UPDATED] Graduation resolution proposal
Sentence got cut when sending : (Updated the initial draft by removing paragraph on "task to adopt a set of bylaws") On Sun, Sep 2, 2018 at 12:22 PM Jim Jagielski wrote: > +1 (binding)! :) > > > On Sep 2, 2018, at 3:18 PM, Matteo Merli wrote: > > > > Updated the initial draft by removing paragraph on the "have a tasking > for > > creating set of bylaws". > > > > > > > > Establish the Apache Pulsar Project > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > the Foundation and consistent with the Foundation's purpose to establish > > a Project Management Committee charged with the creation and maintenance > > of open-source software, for distribution at no charge to the public, > > related to a highly scalable, low latency messaging platform running on > > commodity hardware. It provides simple pub-sub and queue semantics over > > topics, lightweight compute framework, automatic cursor management for > > subscribers, and cross-datacenter replication. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache Pulsar Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache Pulsar Project be and hereby is responsible > > for the creation and maintenance of software related to a highly > > scalable, low latency messaging platform running on commodity hardware. > > It provides simple pub-sub and queue semantics over topics, lightweight > > compute framework, automatic cursor management for subscribers, and > > cross-datacenter replication; and be it further > > > > RESOLVED, that the office of "Vice President, Apache Pulsar" be and > > hereby is created, the person holding such office to serve at the > > direction of the Board of Directors as the chair of the Apache Pulsar > > Project, and to have primary responsibility for management of the > > projects within the scope of responsibility of the Apache Pulsar > > Project; and be it further > > > > RESOLVED, that the persons listed immediately below be and hereby are > > appointed to serve as the initial members of the Apache Pulsar Project: > > > > * Boyang Jerry Peng > > * Brad McMillen > > * David Fisher > > * Francis Christopher Liu > > * Hiroyuki Sakai > > * Ivan Brendan Kelly > > * Jai Asher > > * Jia Zhai > > * Jim Jagielski > > * Joe Francis > > * Ludwig Pummer > > * Masahiro Sakamoto > > * Masakazu Kitajo > > * Matteo Merli > > * Nozomi Kurihara > > * P. Taylor Goetz > > * Rajan Dhabalia > > * Sahaya Andrews > > * Sanjeev Kulkarni > > * Sebastián Schepens > > * Siddharth Boobna > > * Sijie Guo > > * Yuki Shiga > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed > > to the office of Vice President, Apache Pulsar, to serve in accordance > > with and subject to the direction of the Board of Directors and the > > Bylaws of the Foundation until death, resignation, retirement, removal > > or disqualification, or until a successor is appointed; and be it > > further > > > > RESOLVED, that the Apache Pulsar Project be and hereby is tasked with > > the migration and rationalization of the Apache Incubator Pulsar > > podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > Pulsar podling encumbered upon the Apache Incubator PMC are hereafter > > discharged. > > > > > > > > > > -- > > Matteo Merli > > > > -- Matteo Merli
Re: [DRAFT] [UPDATED] Graduation resolution proposal
Updated the initial draft by removing paragraph on the "have a tasking for creating set of bylaws". Establish the Apache Pulsar Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub and queue semantics over topics, lightweight compute framework, automatic cursor management for subscribers, and cross-datacenter replication. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Pulsar Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Pulsar Project be and hereby is responsible for the creation and maintenance of software related to a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub and queue semantics over topics, lightweight compute framework, automatic cursor management for subscribers, and cross-datacenter replication; and be it further RESOLVED, that the office of "Vice President, Apache Pulsar" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Pulsar Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Pulsar Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Pulsar Project: * Boyang Jerry Peng * Brad McMillen * David Fisher * Francis Christopher Liu * Hiroyuki Sakai * Ivan Brendan Kelly * Jai Asher * Jia Zhai * Jim Jagielski * Joe Francis * Ludwig Pummer * Masahiro Sakamoto * Masakazu Kitajo * Matteo Merli * Nozomi Kurihara * P. Taylor Goetz * Rajan Dhabalia * Sahaya Andrews * Sanjeev Kulkarni * Sebastián Schepens * Siddharth Boobna * Sijie Guo * Yuki Shiga NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed to the office of Vice President, Apache Pulsar, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Pulsar Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Pulsar podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Pulsar podling encumbered upon the Apache Incubator PMC are hereafter discharged. ---- -- Matteo Merli
Re: [DRAFT] Graduation resolution proposal
On Sun, Sep 2, 2018 at 11:59 AM Dave Fisher wrote: > Hi Matteo - > > The BookKeeper bylaws are a problem in that the PMC Emeritus process is > not the Apache Way. Merit does not expire and numerous projects would be in > trouble if those were the wide rules. It may not cause trouble for a PMC in > the future. Not now as everything is good, but sooner or latter it may > become grounds for trouble in the community. This is a foundation wide > governance issue. IHMO - It is a bug in Whimsy. Which is why I brought it > where I did. As such keep in mind that Jim has a very valid point. He is a > Founder of the ASF and until this year had continually served as a Board > member and/or Officer every year. > > Let’s remove the clause from the Resolution. > +1 -- I'll update draft Willing to discuss it with Sijie and Ivan on those lists.> > I didn't want to bring trouble also on BookKeeper :) -- Matteo Merli
Re: Slack
On Fri, Aug 31, 2018 at 7:16 PM Dave Fisher wrote: > Hi - > > Regarding Slack. Is this a free account? Who on the PPMC has control? > Yes, the account is free. I created it initially and most people from the PPMC have admin status on the instance. You Dave are also marked as admin. Back when we started I was adding everyone from PPMC when registered to Slack. If there's anyone missing, any other "admin" can promote other regular users into "admins" as well. > Matteo - how do you run the daily script to send a digest of Slack > conversations to dev@? > Currently, is running as a cron job from a private EC2 instance. I initially tried to run it from ASF Jenkins but I had issues with the couple of Python dependencies that the script needs. I guess, it might be a good idea to run the script from a Docker image, so that it becomes easier to run on Jenkins. Script is still at https://github.com/merlimat/slack-email-digest Matteo > > Regards, > Dave > > Sent from my iPhone > -- Matteo Merli
Re: [DRAFT] Graduation resolution proposal
Thanks Dave for asking the question in bigger forum. As mentioned, for the draft, I just followed the text suggested by the whimsy tool, which I've seen included in multiple recent resolutions. My understanding of that paragraph is that "once the PMC is formed one of its first tasks would be to figure out what it wants to do with respect to bylaws, whether to adopt standard ASF bylaws or have a modified version discussed and voted by PMC". If the consensus is to leave this paragraph out of the draft, we can certainly remove from draft. To comment on Taylor's question: >> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required), or are the Apache defaults acceptable? >> One option is to simply not have bylaws, which means you would simply adhere to [1] and [2], and put any clarifications in a contributors’ guide (which you’ve done). I am personally fine with Apache defaults, though I find it useful to have (like many projects do) a page with explicit ByLaws, with details on what is the process for different "actions" (eg: code changes, releases, committer). One such example, that I'm familiar with is BookKeeper ( http://bookkeeper.apache.org/project/bylaws/). Matteo On Sun, Sep 2, 2018 at 9:32 AM Dave Fisher wrote: > Hi - > > I’m bringing Taylor’s comment to general@incubator so that we can get > consensus to get the whimsy tool changed. > > Regards, > Dave > > > On Sep 2, 2018, at 8:33 AM, Jim Jagielski wrote: > > > > I would agree. I think that we should NOT add anything about PMC > specific bylaws in our resolution. I would even go so far as to vote -1 on > the resolution with that clause included. > > > >> On Aug 31, 2018, at 4:16 PM, P. Taylor Goetz wrote: > >> > >> I would like to stay on as well. > >> > >> Quick question: > >> > >>> RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked > >>> with the creation of a set of bylaws intended to encourage open > >>> development and increased participation in the Apache Pulsar Project; > >>> and be it further > >> > >> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required), > or are the Apache defaults acceptable? > >> > >> One option is to simply not have bylaws, which means you would simply > adhere to [1] and [2], and put any clarifications in a contributors’ guide > (which you’ve done). > >> > >> -Taylor > >> > >> [1] http://www.apache.org/foundation/voting.html < > http://www.apache.org/foundation/voting.html> > >> [2] http://www.apache.org/dev/pmc.html < > http://www.apache.org/dev/pmc.html> > >> > >>> On Aug 31, 2018, at 12:43 PM, Matteo Merli mme...@apache.org>> wrote: > >>> > >>> I have prepared the draft for the graduation resolution using the > >>> Whimsy tool (https://whimsy.apache.org/roster/ppmc/pulsar < > https://whimsy.apache.org/roster/ppmc/pulsar>). > >>> > >>> Maturity model self-assessment is at > >>> > https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar > < > https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar > > > >>> Contributing to Pulsar page is now available at > >>> http://pulsar.incubator.apache.org/contributing/ > >>> > >>> Notes: > >>> > >>> * I'm proposing myself as initial PMC chair -- Please comment if > >>> community is onboard with this or propose other persons as well > >>> > >>> * This draft includes all existing PPMC members and mentors into the > new PMC. > >>> > >>>- For all: please indicate if you want to keep being part of the > >>> PMC or if you prefer to be removed. > >>> > >>> > >>> > >>> > >>> Establish the Apache Pulsar Project > >>> > >>> WHEREAS, the Board of Directors deems it to be in the best interests of > >>> the Foundation and consistent with the Foundation's purpose to > establish > >>> a Project Management Committee charged with the creation and > maintenance > >>> of open-source software, for distribution at no charge to the public, > >>> related to a highly scalable, low latency messaging platform running on > >>> commodity hardware. It provides simple pub-sub and queue semantics over > >>> topics, lightweight compute framework, automatic cursor management for > >
[DRAFT] Graduation resolution proposal
I have prepared the draft for the graduation resolution using the Whimsy tool (https://whimsy.apache.org/roster/ppmc/pulsar). Maturity model self-assessment is at https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar Contributing to Pulsar page is now available at http://pulsar.incubator.apache.org/contributing/ Notes: * I'm proposing myself as initial PMC chair -- Please comment if community is onboard with this or propose other persons as well * This draft includes all existing PPMC members and mentors into the new PMC. - For all: please indicate if you want to keep being part of the PMC or if you prefer to be removed. Establish the Apache Pulsar Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub and queue semantics over topics, lightweight compute framework, automatic cursor management for subscribers, and cross-datacenter replication. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Pulsar Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Pulsar Project be and hereby is responsible for the creation and maintenance of software related to a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub and queue semantics over topics, lightweight compute framework, automatic cursor management for subscribers, and cross-datacenter replication; and be it further RESOLVED, that the office of "Vice President, Apache Pulsar" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Pulsar Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Pulsar Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Pulsar Project: * Boyang Jerry Peng * Brad McMillen * David Fisher * Francis Christopher Liu * Hiroyuki Sakai * Ivan Brendan Kelly * Jai Asher * Jia Zhai * Jim Jagielski * Joe Francis * Ludwig Pummer * Masahiro Sakamoto * Masakazu Kitajo * Matteo Merli * Nozomi Kurihara * P. Taylor Goetz * Rajan Dhabalia * Sahaya Andrews * Sanjeev Kulkarni * Sebastián Schepens * Siddharth Boobna * Sijie Guo * Yuki Shiga NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed to the office of Vice President, Apache Pulsar, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Pulsar Project; and be it further RESOLVED, that the Apache Pulsar Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Pulsar podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Pulsar podling encumbered upon the Apache Incubator PMC are hereafter discharged. -------- -- Matteo Merli -- Matteo Merli
Re: [DISCUSSION] Pulsar maturity model assessment
Thanks both David and Taylor for the support. I think too that it would be good to have few mentors continuing being involved in the project. Once the "contributing" PR is merged and the website is updated (we're waiting on Jenkins to come back up at this point), then I will start the VOTE thread on this list to formalize the Pulsar community position. Matteo On Thu, Aug 30, 2018 at 4:39 PM P. Taylor Goetz wrote: > For the record, I’m supportive of graduation for Pulsar at this point. > > I think the branding debacle and the maturity model self-assessment has > forced some good introspection on the part of the PPMC in terms of what’s > expected of them as a TLP, and I think they are ready. > > I would like to see a mentor or two continue with the project > post-graduation. > > -Taylor > > > On Aug 30, 2018, at 6:51 PM, Dave Fisher wrote: > > > > +1 from me as well. > > > > Regards, > > Dave > > > >> On Aug 30, 2018, at 2:54 PM, P. Taylor Goetz wrote: > >> > >> +1from me. Nice work. > >> > >> -Taylor > >> > >>> On Aug 30, 2018, at 5:32 PM, Matteo Merli wrote: > >>> > >>> Dave, > >>> > >>> I have reworded a bit the "becoming committer" section by adding this > >>> paragraph: > >>> > >>> > >>> Every new committer has to be proposed by a current committer and then > >>> privately discussed and voted in by the members of the Pulsar PMC. > >>> For details about this process and for candidate requirements see the > >>> general [Apache guidelines for assessing new candidates for > committership]( > >>> https://community.apache.org/newcommitter.html). > >>> Candidates prepare for their nomination as committer by contributing > >>> to the Pulsar project and its community, by acting according to the > >>> [Apache Way](https://www.apache.org/foundation/how-it-works.html), > >>> and by generally following the path from > >>> [contributor to committer](https://community.apache.org/contributors/) > >>> for Apache projects. > >>> > >>> > >>> This is the last commit diff > >>> > https://github.com/apache/incubator-pulsar/pull/2459/commits/0bef7eb7f7687ef5d1574f4fb58ff9a69d8a31fa > >>> > >>> Please take a look, > >>> > >>> thanks, > >>> Matteo > >>> > >>>> On Wed, Aug 29, 2018 at 11:06 AM Dave Fisher > wrote: > >>>> > >>>> Hi - > >>>> > >>>> The explanation should be more carefully worded. Contributors do not > self > >>>> nominate themselves. The PMC will notice contributors who have proven > >>>> themselves. A discussion follows on private@ to avoid any > embarrassment. > >>> > >>> Assuming that the VOTE passes if it is for PMC then a NOTICE is given > to > >>>> the IPMC or the Board. This is a 72 hour LAZY ACK in the extremely > rare > >>>> case someone knows something that is bad. You don’t need to explain > these > >>>> details. Once the new Committer and/or PMC has been elected. The PMC > will > >>>> contact them off list to make sure that they accept. This is followed > by an > >>>> announcement on the dev@ list. The whole point here is to avoid > public > >>>> embarrassment which could cause contributors to leave. > >>>> > >>>> For example, the DISCUSSION (on private@) could be like so: > >>>> 1. [DISCUSS] Jane Doe for PMC - she’s done some significant work and > it is > >>>> all high quality. She is good to work with and always helpful with > users on > >>>> the mailing list. > >>>> 2. RE: - She’s great +1 > >>>> 3. RE2: - I’m not sure as she’s only been active for one month. Let’s > wait > >>>> a few months to see if her contributions are sustained. > >>>> … two months, > >>>> 4. [DISCUSS] Jane Doe for PMC/Committer - it’s been two months and > she’s > >>>> still helping with code and users. Is it time. > >>>> 5. RE: yes! > >>>> 6. RE2: yes! > >>>> … 72 hours > >>>> 7. [VOTE] …. > >>>> … 72 hours > >>>> 8. [NOTICE] > >>>> … 72 hours > >>>> 9. Invite Jane > >>>> 10. Jane is surprised and accepts > >>>> 11. Announce on Dev
Re: [DISCUSSION] Pulsar maturity model assessment
Dave, I have reworded a bit the "becoming committer" section by adding this paragraph: Every new committer has to be proposed by a current committer and then privately discussed and voted in by the members of the Pulsar PMC. For details about this process and for candidate requirements see the general [Apache guidelines for assessing new candidates for committership]( https://community.apache.org/newcommitter.html). Candidates prepare for their nomination as committer by contributing to the Pulsar project and its community, by acting according to the [Apache Way](https://www.apache.org/foundation/how-it-works.html), and by generally following the path from [contributor to committer](https://community.apache.org/contributors/) for Apache projects. This is the last commit diff https://github.com/apache/incubator-pulsar/pull/2459/commits/0bef7eb7f7687ef5d1574f4fb58ff9a69d8a31fa Please take a look, thanks, Matteo On Wed, Aug 29, 2018 at 11:06 AM Dave Fisher wrote: > Hi - > > The explanation should be more carefully worded. Contributors do not self > nominate themselves. The PMC will notice contributors who have proven > themselves. A discussion follows on private@ to avoid any embarrassment. Assuming that the VOTE passes if it is for PMC then a NOTICE is given to > the IPMC or the Board. This is a 72 hour LAZY ACK in the extremely rare > case someone knows something that is bad. You don’t need to explain these > details. Once the new Committer and/or PMC has been elected. The PMC will > contact them off list to make sure that they accept. This is followed by an > announcement on the dev@ list. The whole point here is to avoid public > embarrassment which could cause contributors to leave. > > For example, the DISCUSSION (on private@) could be like so: > 1. [DISCUSS] Jane Doe for PMC - she’s done some significant work and it is > all high quality. She is good to work with and always helpful with users on > the mailing list. > 2. RE: - She’s great +1 > 3. RE2: - I’m not sure as she’s only been active for one month. Let’s wait > a few months to see if her contributions are sustained. > … two months, > 4. [DISCUSS] Jane Doe for PMC/Committer - it’s been two months and she’s > still helping with code and users. Is it time. > 5. RE: yes! > 6. RE2: yes! > … 72 hours > 7. [VOTE] …. > … 72 hours > 8. [NOTICE] > … 72 hours > 9. Invite Jane > 10. Jane is surprised and accepts > 11. Announce on Dev@ and maybe twitter. > > So, you can see ways to tweak your language. > > Regards, > Dave > > > On Aug 29, 2018, at 12:16 AM, Matteo Merli > wrote: > > > > On Tue, Aug 28, 2018 at 5:50 PM Dave Fisher > wrote: > > > >> This is very detailed and looks good with one important omission. > >> > >> How does one go on from being a contributor to committer / PMC status? > >> There should be a description about that. > >> > >> Please discuss! > >> > > > > That is a very good point. I have added a couple of sections to the > > "Contributing" page in the PR: > > * https://github.com/apache/incubator-pulsar/pull/2459 > > * Preview link: > > > https://github.com/apache/incubator-pulsar/blob/0515a9a12a77ca6ffdc8587125e21a32cdb61291/site2/website/contributing.md > > > > Also reporting it here for convenience: > > > > > --- > > ## Becoming a committer > > > > Committers are community members that have write access to the project’s > > repositories, i.e., they can modify the code, documentation, and website > > by themselves and also accept other contributions. > > > > There is no strict protocol for becoming a committer. Candidates for new > > committers are typically people that are active contributors and > > community members. > > > > Being an active community member means participating on mailing list > > discussions, helping to answer questions, verifying release candidates, > > being respectful towards others, and following the meritocratic > > principles of community management. Since the > > [Apache Way](https://www.apache.org/foundation/governance/) > > has a strong focus on the project community, this part is very important. > > > > Of course, contributing code and documentation to the project is > > important as well. A good way to start is contributing improvements, new > > features, or bug fixes. You need to show that you take responsibility > > for the code that you contribute, add tests and documentation, and help > > maintaining it. > > > > Candidates for new committers are sugges
Re: [DISCUSSION] Pulsar maturity model assessment
On Tue, Aug 28, 2018 at 5:50 PM Dave Fisher wrote: > This is very detailed and looks good with one important omission. > > How does one go on from being a contributor to committer / PMC status? > There should be a description about that. > > Please discuss! > That is a very good point. I have added a couple of sections to the "Contributing" page in the PR: * https://github.com/apache/incubator-pulsar/pull/2459 * Preview link: https://github.com/apache/incubator-pulsar/blob/0515a9a12a77ca6ffdc8587125e21a32cdb61291/site2/website/contributing.md Also reporting it here for convenience: --- ## Becoming a committer Committers are community members that have write access to the project’s repositories, i.e., they can modify the code, documentation, and website by themselves and also accept other contributions. There is no strict protocol for becoming a committer. Candidates for new committers are typically people that are active contributors and community members. Being an active community member means participating on mailing list discussions, helping to answer questions, verifying release candidates, being respectful towards others, and following the meritocratic principles of community management. Since the [Apache Way](https://www.apache.org/foundation/governance/) has a strong focus on the project community, this part is very important. Of course, contributing code and documentation to the project is important as well. A good way to start is contributing improvements, new features, or bug fixes. You need to show that you take responsibility for the code that you contribute, add tests and documentation, and help maintaining it. Candidates for new committers are suggested by current committers or PMC members, and voted upon by the PMC. If you would like to become a committer, you should engage with the community and start contributing to Apache Pulsar in any of the above ways. You might also want to talk to other committers and ask for their advice and guidance. ## Becoming member of PMC The PMC is the project governance body. Committers or contributors that have demonstrated continued involvement with the community can be nominated to become members of the PMC. PMC members nominate new contributors to the project as either committers or as new PMC members, and PMC members cast votes on electing new committers or PMC members to the project. PMC members also have binding votes on any project matters. Refer to [ASF PMCs governance](http://www.apache.org/foundation/governance/pmcs.html) for a more detailed explanation of the duties and roles of the PMC. --- > This is better and ties in with my main question above. > Created a separate PR to update the "team" page: https://github.com/apache/incubator-pulsar/pull/2470 Matteo -- Matteo Merli
Re: [DISCUSSION] Pulsar maturity model assessment
On Tue, Aug 28, 2018 at 5:04 PM Dave Fisher wrote: > Hi - > > The contributing guide is a 404 on the website and I don’t see it on the > menus. (Is it translated? I thought I saw an initial commit for it > yesterday. The PR is still not merged. Waiting for some flaky tests on CI to let it go through: PR - https://github.com/apache/incubator-pulsar/pull/2459 Preview of contributing page: https://github.com/apache/incubator-pulsar/blob/d27d387ab3fe9a2aef997bad1b474fa92b466a05/site2/website/contributing.md > The descriptions on the team page are a little off - Members are both > Committers and PPMC members. Please make that distinct. (In the ASF there > is a difference between an Apache Member and a PMC Member.) > This description was actually coming from BookKeeper team page :) and I can see it's being used in multiple projects (eg: HiveMail https://hivemall.incubator.apache.org/team-list.html, or Maven https://maven.apache.org/team.html ). I am perfectly fine to change the description, because I agree that usage of "members" is not very clear to whom it refers to. What about changing the description into : -- A successful project requires many people to play many roles. Some write code or documentation, while others are valuable as testers, submitting patches and suggestions. The team is comprised of PMC members, Committers and Contributors. Committers have direct access to the source of a project and actively evolve the codebase. Contributors improve the project through submission of patches and suggestions to be reviewed by the Committers. The number of Committers and Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated. -- Matteo -- Matteo Merli
Re: Accidently pushed a change to branch-1.22
On Tue, Aug 28, 2018 at 9:10 AM Dave Fisher wrote: > What was released as 1.22 is still tagged and available as such in Git? > > Reasoning is you don’t want confusion about what was truly released. > > It depends on how users might pick up 1.22. > Yes, the release is still tagged as `v1.22.1-incubating` and that will not change. The branch is called `branch-1.22` though it's not really advertised to users. Fetching from a branch is similar to fetching from `master` and doesn't guarantee to get any particular version. -- Matteo Merli
Re: Accidently pushed a change to branch-1.22
I would say to leave it there. If someone will want to to a 1.22.2 release it would be a good idea to include it. On Tue, Aug 28, 2018 at 5:28 AM Ivan Kelly wrote: > Hi folks, > > I accidently pushed a change to branch-1.22 to fix #2401. > > > https://github.com/apache/incubator-pulsar/commit/92b809784f631bc6b72cc1116761e8fac02ef41c > > Should I revert immediately? It's a pretty straightforward change > given what the bug was. > > -Ivan > -- Matteo Merli
[DISCUSSION] Pulsar maturity model assessment
I have started a draft of the maturity model assessment. You can find it on the wiki: https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar Please review it and provide feedback. Once there is agreement on this document, I think we should then do a vote to formalize the community position regarding TLP graduation. Matteo -- Matteo Merli
Re: Starting the Graduation Process
Hi Dave, I'm looking at all the documentation. I'll send a draft later today. Matteo On Mon, Aug 27, 2018 at 10:57 AM Dave Fisher wrote: > You’re welcome. > > Anyone working on the maturity analysis? > > Regards, > Dave > > > On Aug 23, 2018, at 5:26 PM, Matteo Merli > wrote: > > > > Thanks Dave for starting the discussion. > > On Thu, Aug 23, 2018 at 5:25 PM Joe F wrote: > > > >> +1🎓 > >> > >> On Thu, Aug 23, 2018 at 5:22 PM Sijie Guo wrote: > >> > >>> On Thu, Aug 23, 2018 at 5:17 PM Dave Fisher wrote: > >>> > >>>> Hi - > >>>> > >>>> I think that the Pulsar community is just about ready to graduate to a > >>> Top > >>>> Level Project. > >>>> > >>>> The graduation guide is here. [1] > >>>> The incubation status file is here. [2] I made some changes today > which > >>>> have yet to propagate. They should by tomorrow. > >>>> The Community Development project has maturity model self assessment. > >> [3] > >>>> It is recommended that the project do this assessment recording > answers > >>> in > >>>> the Wiki. > >>>> > >>>> Let’s get this started! > >>> > >>> > >>> 🎉🎉 +1 to start the process > >>> > >>> > >>>> > >>>> Regards, > >>>> Dave > >>>> > >>>> [1] https://incubator.apache.org/guides/graduation.html > >>>> [2] https://incubator.apache.org/projects/pulsar.html > >>>> [3] > >>>> > >>> > >> > https://community.apache.org/apache-way/apache-project-maturity-model.html > >>>> > >>> > >> > > -- > > Matteo Merli > > > > -- Matteo Merli
Re: PIP 23 : Message Tracing By Interceptors
> Original, i just want to implement tracing by interceptors. We don’t must > to binding “tracing” and “interceptors” together. > I thougt that to implement message tracing in pulsar, we should implement > interceptors before. And interceptors might be useful in multiple scenarios. Yes, that's exactly what I meant. Interceptors are a good feature to have in general and tracing can be implemented on top of that. I think we should probably separate the 2 aspects and have this proposal just focus on interceptors. One other thing to consider is that for tracing to be "meaningful" we would also need to have support in broker side (and, as you mentioned, ideally in bookkeeper as well). That means that either: * We provide "interceptors" hooks also for broker * or we have some "fixed" tracing implementation that we support. In any case, my previous example was to show how, as a user, I'd like the enabling tracing in Pulsar should be. Since tracing will be a very common feature, we should aim to have a tight integration with few common tracing providers, while leaving the freedom for user to integrate with custom tracing systems. Matteo On Fri, Aug 24, 2018 at 3:02 AM 李鹏辉 wrote: > Original, i just want to implement tracing by interceptors. We don’t must > to binding “tracing” and “interceptors” together. > > I thougt that to implement message tracing in pulsar, we should implement > interceptors before. And interceptors might be useful in multiple > scenarios. > -- Matteo Merli
Re: PIP 23 : Message Tracing By Interceptors
Hi Penghui,
the proposal looks good to me. I like the approach of using interceptors
since they might be useful in multiple scenarios, for applications to add
custom logging or processing.
For tracing, in particular, I think we should also aim to have "out of the
box" ready made solution as well, especially targeting standard APIs like
OpenTracing. We shouldn't be dictating any particular implementation, but
we should try to avoid the burden of integrating with tracing APIs to
application developers.
Ideally, as a user, I should be able to do something like :
client.newConsumer()
.topic("xyz")
.subscriptionName("yyz")
.withTracing(OpenTracing.of(tracingLoggerConfig))
.subscribe();
(Or maybe even configure that at the PulsarClient level)
On Tue, Aug 21, 2018 at 11:13 AM Sijie Guo wrote:
> Updated. Thanks, Penghui!
>
> - Sijie
>
> On Tue, Aug 21, 2018 at 3:56 AM 李鹏辉 wrote:
>
> > Please add zhaijia to Authors.
> >
> > Sijie Guo 于2018年8月21日周二 下午6:48写道：
> >
> > > Thank you penghui! This is a great feature to add to Pulsar.
> > >
> > > I've copied your PIP to pulsar wiki as well :
> > >
> > >
> >
> https://github.com/apache/incubator-pulsar/wiki/PIP-23:-Message-Tracing-By-Interceptors
> > >
> > > - Sijie
> > >
> > > On Tue, Aug 21, 2018 at 3:14 AM 李鹏辉 wrote:
> > >
> > > > Dear all
> > > >
> > > > This is a PIP to add feature of message trace implement by
> > interceptors.
> > > >
> > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1aigUKZ-AhQvugOfzUzypyMMeXfum5XlNkwuYK4KvxJs/edit?usp=sharing
> > > >
> > > > —
> > > > Regards,
> > > > Penghui Li
> > > >
> > >
> >
>
--
Matteo Merli
Re: Starting the Graduation Process
Thanks Dave for starting the discussion. On Thu, Aug 23, 2018 at 5:25 PM Joe F wrote: > +1🎓 > > On Thu, Aug 23, 2018 at 5:22 PM Sijie Guo wrote: > > > On Thu, Aug 23, 2018 at 5:17 PM Dave Fisher wrote: > > > > > Hi - > > > > > > I think that the Pulsar community is just about ready to graduate to a > > Top > > > Level Project. > > > > > > The graduation guide is here. [1] > > > The incubation status file is here. [2] I made some changes today which > > > have yet to propagate. They should by tomorrow. > > > The Community Development project has maturity model self assessment. > [3] > > > It is recommended that the project do this assessment recording answers > > in > > > the Wiki. > > > > > > Let’s get this started! > > > > > > 🎉🎉 +1 to start the process > > > > > > > > > > Regards, > > > Dave > > > > > > [1] https://incubator.apache.org/guides/graduation.html > > > [2] https://incubator.apache.org/projects/pulsar.html > > > [3] > > > > > > https://community.apache.org/apache-way/apache-project-maturity-model.html > > > > > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5
On Mon, Jul 23, 2018 at 11:12 AM Dave Fisher wrote: > (3) Pulsar IO Connectors NAR files. > Signature and checksums pass. > LICENSE and DISCLAIMER exist in the top level of the package. > LICENSE and NOTICE plus DEPENDENCIES exist in the NAR files. > > ==> DISCLAIMER should be included in the NAR files. > ==> NOTICE should also be at the top level. > It's a bit tricky to add these. We are using the Apache NiFi NAR maven plugin to generate the archives. To add custom files, we would probably have to customize the plugin itself. > (4) DEB > Signature and checksums pass > NOTICE, LICENSE, and DISCLAIMER look good. > > ==> copyright files contain the Apache License. IMO these ought to contain > the NOTICE > Yes, I was a bit confused by this. My understanding was that in Debian convention the 'copyright' file contains the license. I left both LICENSE and 'copyright' just to be on the safe side. (5) RPM > Signature and checksums pass > NOTICE, LICENSE, and DISCLAIMER look good. > > ==> I’m curious about how the sqlite binary files are used. > The sqlite binary files (and similarly the Packages.gz for Debian) are used by the package manages (yum or apt-get) to fetch the metadata of the available packages. The idea would be for users to first import the YUM repository and then do the regular `yum install apache-pulsar-client`. Once the binaries are available on mirrors, we'll be adding instructions, similar to what Cassandra has for rpm/deb files at http://cassandra.apache.org/download/ Matteo -- Matteo Merli
Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5
;>>> - Pulsar I/O: a serverless connector framework built on top of > > Pulsar > > >>>>>> Functions. > > >>>>>> - TieredStorage: offloads bookkeeper ledgers to a cold storage > (like > > >>> S3). > > >>>>>> - Stateful Function: Pulsar Functions supports storing state back > to > > >>>>>> bookkeeper. > > >>>>>> - Go Client: a Go client wrapping over existing cpp client. > > >>>>>> - Avro and Protobuf schema are supported. > > >>>>>> > > >>>>>> Full list of changes and fixes are available: > > >>>>>> > > >>>>>> https://github.com/apache/incubator-pulsar/milestone/13?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/incubator/pulsar/pulsar-2.1.0-incubating-candidate-5/ > > >>>>>> > > >>>>>> SHA-1 checksums: > > >>>>>> > > >>>>>> f0f6b6d7c48d119da36fc4fa1f934fd1f9ba8498 > > >>>>>> ./apache-pulsar-2.1.0-incubating-bin.tar.gz > > >>>>>> > > >>>>>> b6a968249a7c5d21be89ece27895b862efda9a92 > > >>>>>> ./apache-pulsar-2.1.0-incubating-src.tar.gz > > >>>>>> > > >>>>>> ddcf929eb18082ff2b9979507054453e8e803ed3 > > >>>>>> ./apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz > > >>>>>> > > >>>>>> > > >>>>>> Maven staging repo: > > >>>>>> > > >>> > > https://repository.apache.org/content/repositories/orgapachepulsar-1025/ > > >>>>>> > > >>>>>> The tag to be voted upon: > > >>>>>> v2.1.0-incubating-candidate-5 > > >>> (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177) > > >>>>>> > > >>>>> > > >>> > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.1.0-incubating-candidate-5 > > >>>>>> > > >>>>>> Pulsar's KEYS file containing PGP keys we use to sign the release: > > >>>>>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > >>>>>> > > >>>>>> Please download the the source package, and follow the README to > > build > > >>>>>> and run the Pulsar standalone service. > > >>>>>> > > >>>>>> A few notes for reviewing/voting 2.1.0 release: > > >>>>>> > > >>>>>> - Starting from this release, we are shipping RPM & DEB packages > for > > >>>>> pulsar > > >>>>>> non-java clients. > > >>>>>> - Starting from this release, we are 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, I put up an > > >>>>>> instruction for people to validate release candidate > > >>>>>> on different features: > > >>>>>> > > >>>>> > > >>> > > > https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation > > >>>>> > > >>>>> > > >>> > > >>> > > > > > -- Matteo Merli
Re: DEB and RPM release artifacts and their naming
Hi Dave, I have mostly based the RPM on what Cassandra was doing to distribute RPMs ( http://cassandra.apache.org/download/) The idea is to have YUM (for RPM) and Apt-Get (for Deb) repositories that can be added and then packages can be installed automatically, with checksums and signatures validated. The `Packages.gz` and `RPMS/repodata` are there to make the directory a valid repository for packages. These are generated by respective tools: * For RPMs : https://github.com/apache/incubator-pulsar/blob/master/pulsar-client-cpp/pkg/rpm/build-rpm.sh#L43 * For Deb : https://github.com/apache/incubator-pulsar/blob/master/pulsar-client-cpp/pkg/deb/build-deb.sh#L95 Regarding `pulsar-client` vs `apache-pulsar-client` and including `incubating` in the package release, I've opened a PR to address that https://github.com/apache/incubator-pulsar/pull/2129 Thanks, Matteo On Mon, Jul 2, 2018 at 10:13 AM Dave Fisher wrote: > Hi - > > Pulsar plans to release DEB and RPM convenience binaries and we need to > discuss the artifacts. How they are named and why each one is required. > > My experience with releasing these types of binaries is from OpenOffice > where we have released DEB and RPM binaries for a long time. See > http://archive.apache.org/dist/openoffice/4.1.5/binaries/en-US/ > > Starting from here: > https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.0-incubating-candidate-4/ > > Look into both the DEB and RPMS directories and note that both “apache-" > and “-incubating" are missing from the names. Unless there is good reasons > that are explained with the explanation accepted then the names need to be > changed in the next release candidate. > > What is “Packages.gz” in the DEB directory? Is that name prescriptive? > > Please explain repodata in the RMPS/repodata directory. > > Regards, > Dave > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 4
+1 Binding Checked: * Signatures * RAT * LICENSE / NOTICE for src/bin * RPM/Deb packages * Started standalone * Maven staging repository Matteo On Fri, Jun 29, 2018 at 2:37 AM Sijie Guo wrote: > This is the 4th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/13?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/incubator/pulsar/pulsar-2.1.0-incubating-candidate-4/ > > SHA-1 checksums: > > 514d1c384c752d74a9e72fb60a06be1c2f632824 > apache-pulsar-2.1.0-incubating-bin.tar.gz > > e73fba881bc26d98ea9dd5eaaf0cd7ecd4d305d9 > apache-pulsar-2.1.0-incubating-src.tar.gz > > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1024/ > > The tag to be voted upon: > v2.1.0-incubating-candidate-4 (d3261ed4dc86f4cdf5ad6a246c532212f064967a) > > https://github.com/apache/incubator-pulsar/releases/tag/v2.1.0-incubating-candidate-4 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > > NOTES: starting from this release, we are shipping RPM & DEB packages for > pulsar cpp > clients along with the source and binary tarballs. > > - Sijie > -- Matteo Merli
[RESULT] [VOTE] Maintaining "Apache Pulsar" name
This vote is now closed: 9 binding +1s: * Matteo Merli * Rajan Dhabalia * Nozomi Kurihara * Sanjeev Kulkarni * Sijie Guo * Joe Francis * Jia Zhai * Masakazu Kitajo * Ivan Kelly 1 non-binding +1 : * Ali Ahmed I'll now notify trademarks@ regarding the decision. Thanks, Matteo On Thu, Jun 21, 2018 at 10:28 AM Ivan Kelly wrote: > +1 > > On Thu, Jun 21, 2018 at 2:06 AM, Matteo Merli wrote: > > Following the previous discussion at > > > https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf9772677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E > > I am calling a formal vote for keep using "Apache Pulsar" name for the > > project. > > > > This vote will be open for at least 72 hours. After that we will > > communicate the decision to trademarks@apache > > > > +1 from me > > > > Matteo > > -- > > Matteo Merli > > > -- Matteo Merli
Client features matrix wiki page
I have started a wiki page to recap which features are supported in the different client libraries. https://github.com/apache/incubator-pulsar/wiki/Client-Features-Matrix Please take a look and add missing features. Suggestion on how to improve the page are also welcome :) Matteo -- Matteo Merli
Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 1
There is an issue with the RPM/Deb packages included. Some symbols for OpenSSL are not found when linking from Go. I'm working on a fix for that. Matteo On Mon, Jun 25, 2018 at 4:25 PM Sijie Guo wrote: > This is the first release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/13?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/incubator/pulsar/pulsar-2.1.0-incubating-candidate-1/ > > SHA-1 checksums: > > 944d65e9ef5862aa4b0d1f75bb73befad497ece9 > apache-pulsar-2.1.0-incubating-bin.tar.gz > eb8ab08fa2feee1346f6b77bc7608bf155688763 > apache-pulsar-2.1.0-incubating-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1021/ > > The tag to be voted upon: > v2.1.0-incubating-candidate-1 (840ad88eff88b22e21e567a889c14d04d6a4d91b) > > https://github.com/apache/incubator-pulsar/releases/tag/v2.1.0-incubating-candidate-1 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > > NOTES: starting from this release, we are shipping RPM & DEB packages for > pulsar cpp > clients along with the source and binary tarballs. > -- Matteo Merli
[VOTE] Maintaining "Apache Pulsar" name
Following the previous discussion at https://lists.apache.org/thread.html/fe60c21b7cdca00918fe25e7ddf9772677342063b9da24c9b84b3329@%3Cdev.pulsar.apache.org%3E I am calling a formal vote for keep using "Apache Pulsar" name for the project. This vote will be open for at least 72 hours. After that we will communicate the decision to trademarks@apache +1 from me Matteo -- Matteo Merli
[ANNOUNCE] Apache Pulsar 2.0.1-incubating released
The Apache Pulsar team is proud to announce Apache Pulsar version 2.0.1-incubating. This release fixes issues reported for 2.0.0-rc1-incubating. 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 subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: https://pulsar.incubator.apache.org/download Release Notes are at: http://pulsar.apache.org/release-notes/#2.0.1-incubating We would like to thank the contributors that made the release possible. Regards, The Pulsar Team DISCLAIMER: Apache Pulsar is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. -- Matteo Merli
Planning for release 2.1
As we are about to release 2.0.1, we have already a batch of new items ready to be released. Biggest ticket items are: * Connector framework * Go client library * Schema support for Avro and Protobuf I'd like to propose to cut the release later this week. Please point out any pending change you want to include in 2.1. Also, is anyone volunteering as release manager for 2.1? Matteo -- Matteo Merli
[RESULT] [VOTE] Pulsar Release 2.0.1-incubating Candidate 2
The vote is now closed and the result is 3 +1s and no -1s: * Matteo Merli * Hiroyuki Sakai * Masahiro Sakamoto Thanks, Matteo On Sun, Jun 10, 2018 at 8:45 PM Masahiro Sakamoto wrote: > +1 (binding) > > Environment: CentOS 7.3 > > * checked sha1, sha512, asc > * ran standalone > * producer/consumer worked normally > * compiling and unit tests succeeded > * rat check > > Masahiro > > -- > Masahiro Sakamoto > Yahoo Japan Corp. > E-mail: massa...@yahoo-corp.jp > -- > > > -Original Message- > > From: Hiroyuki Sakai [mailto:hsa...@yahoo-corp.jp] > > Sent: Friday, June 08, 2018 4:28 PM > > To: dev@pulsar.incubator.apache.org > > Subject: Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2 > > > > +1 (binding) > > > > Environment: MacOS 10.13.4 > > > > Checked: > > - sha1, sha512, asc > > - start standalone service and producer/consumer client test (Src/Bin > > distribution) > > - rat check on Src distribution > > - compile and unit tests on Src distribution > > > > Regards, > > Hiroyuki > > > > -Original Message- > > From: Matteo Merli > > Reply-To: "dev@pulsar.incubator.apache.org" > > > > Date: Friday, June 8, 2018 15:35 > > To: "dev@pulsar.incubator.apache.org" > > Subject: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2 > > > > This is the second release candidate for Apache Pulsar, version > > 2.0.1-incubating. > > > > This is a patch release that fixes few issues identified in previous > > release 2.0.0-rc1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/14?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/incubator/pulsar/pulsar-2.0.1-i > > ncubating-candidate-2/ > > > > SHA-1 checksums: > > > > 5acd63f8aa1fa75f386df7b9fd803a943978e609 > > apache-pulsar-2.0.1-incubating-bin.tar.gz > > 312bc0f1ae170c1d2dc38b1e362fb50f82c00525 > > apache-pulsar-2.0.1-incubating-src.tar.gz > > > > Maven staging repo: > > > > https://repository.apache.org/content/repositories/orgapachepulsar-102 > > 0 > > > > > > The tag to be voted upon: > > v2.0.1-incubating-candidate-2 > > (fd47532380d770e4fd78cabe71dea293fc2f0e06) > > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incubat > > ing-candidate-2 > > > > <https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incuba > > ting-candidate-1> > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to > build > > and run the Pulsar standalone service. > > -- > > Matteo Merli > > > > > > -- Matteo Merli
[VOTE] Pulsar Release 2.0.1-incubating Candidate 2
This is the second release candidate for Apache Pulsar, version 2.0.1-incubating. This is a patch release that fixes few issues identified in previous release 2.0.0-rc1-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/14?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/incubator/pulsar/pulsar-2.0.1-incubating-candidate-2/ SHA-1 checksums: 5acd63f8aa1fa75f386df7b9fd803a943978e609 apache-pulsar-2.0.1-incubating-bin.tar.gz 312bc0f1ae170c1d2dc38b1e362fb50f82c00525 apache-pulsar-2.0.1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1020 The tag to be voted upon: v2.0.1-incubating-candidate-2 (fd47532380d770e4fd78cabe71dea293fc2f0e06) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incubating-candidate-2 <https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incubating-candidate-1> Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
Re: [CANCELED] Pulsar Release 2.0.1-incubating Candidate 1
Thanks Masahiro for double-checking. I have the candidate-2 ready. On Thu, Jun 7, 2018 at 11:15 PM Masahiro Sakamoto wrote: > I applied the following two commits on branch-2.0 locally and ran it. > > -- > commit d77833a479f203af3eeba3f2c97aefb8f818fcea > Author: massakam > Date: Fri Jun 8 01:02:12 2018 +0900 > -- > commit 54eb8a54ef9d5d527e9aa663de117c2fa93ea9a3 > Author: Matteo Merli > Date: Mon Jun 4 15:12:56 2018 -0700 > -- > > It seems to work properly. > > Regards, > > Masahiro > > > -Original Message- > > From: Matteo Merli [mailto:matteo.me...@gmail.com] > > Sent: Friday, June 08, 2018 1:26 PM > > To: dev@pulsar.incubator.apache.org > > Subject: Re: [CANCELED] Pulsar Release 2.0.1-incubating Candidate 1 > > > > Sounds good to me. Does that have any dependencies on changes that are in > > master? Can you try to apply on branch-2.0 and see if it applies cleanly > > and works well? > > > > Thanks > > On Thu, Jun 7, 2018 at 8:59 PM Masahiro Sakamoto > > > wrote: > > > > > If we include that change in 2.0.1, I think we also need to backport > this: > > > https://github.com/apache/incubator-pulsar/pull/1930 > > > > > > Regards, > > > > > > Masahiro > > > > > > > -Original Message- > > > > From: Matteo Merli [mailto:mme...@apache.org] > > > > Sent: Friday, June 08, 2018 12:50 PM > > > > To: dev@pulsar.incubator.apache.org > > > > Subject: [CANCELED] Pulsar Release 2.0.1-incubating Candidate 1 > > > > > > > > Masahiro, thanks for catching this. It was my mistake, I forgot to > > > backport > > > > that change. It is a critical fix, so I think we should include it. > > > > > > > > Canceling this vote. I'll send a new candidate asap. > > > > > > > > On Thu, Jun 7, 2018 at 6:36 PM Masahiro Sakamoto > > > > > > > > > > > wrote: > > > > > > > > > Hi Matteo, > > > > > > > > > > It seems that the following modification has not been backported > > > > > to > > > > > branch-2.0 yet. > > > > > https://github.com/apache/incubator-pulsar/pull/1893 > > > > > Is that okay with you? > > > > > > > > > > Regards, > > > > > > > > > > Masahiro > > > > > > > > > > > -Original Message- > > > > > > From: Matteo Merli [mailto:mme...@apache.org] > > > > > > Sent: Tuesday, June 05, 2018 2:44 PM > > > > > > To: dev@pulsar.incubator.apache.org > > > > > > Subject: [VOTE] Pulsar Release 2.0.1-incubating Candidate 1 > > > > > > > > > > > > This is the first release candidate for Apache Pulsar, version > > > > > > 2.0.1-incubating. > > > > > > > > > > > > This is a patch release that fixes few issues identified in > > > > > > previous > > > > > release > > > > > > 2.0.0-rc1-incubating. > > > > > > > > > > > > It fixes the following issues: > > > > > > https://github.com/apache/incubator-pulsar/milestone/14?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/incubator/pulsar/pulsar-2.0.1 > > > > > > -i > > > > > > ncubating-candidate-1/ > > > > > > > > > > > > SHA-1 checksums: > > > > > > > > > > > > ae1bd6f658ebff0745d5eb82961f400f9872f1da > > > > > > apache-pulsar-2.0.1-incubating-bin.tar.gz > > > > > > 2a22e40f290329ae5fac1d33e9754a67e01e882f > > > > > > apache-pulsar-2.0.1-incubating-src.tar.gz > > > > > > > > > > > > Maven staging repo: > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1 > > > > > > 01 > > > > > > 9 > > > > > > > > > > > > The tag to be voted upon: > > > > > > v2.0.1-incubating-candidate-1 > > > > > > (b18a2689d592ac676ab70a5447cc023e378eda3b) > > > > > > > > > > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incub > > > > > > at > > > > > > ing-candidate-1 > > > > > > > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the > release: > > > > > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > > > > > > > > > Please download the the source package, and follow the README to > > > > > > build > > > > > and > > > > > > run the Pulsar standalone service. > > > > > > -- > > > > > > Matteo Merli > > > > > > > > > > > > > > > -- > > > > Matteo Merli > > > > > > > > > -- > > Matteo Merli > > > -- Matteo Merli
Re: [CANCELED] Pulsar Release 2.0.1-incubating Candidate 1
Sounds good to me. Does that have any dependencies on changes that are in master? Can you try to apply on branch-2.0 and see if it applies cleanly and works well? Thanks On Thu, Jun 7, 2018 at 8:59 PM Masahiro Sakamoto wrote: > If we include that change in 2.0.1, I think we also need to backport this: > https://github.com/apache/incubator-pulsar/pull/1930 > > Regards, > > Masahiro > > > -Original Message- > > From: Matteo Merli [mailto:mme...@apache.org] > > Sent: Friday, June 08, 2018 12:50 PM > > To: dev@pulsar.incubator.apache.org > > Subject: [CANCELED] Pulsar Release 2.0.1-incubating Candidate 1 > > > > Masahiro, thanks for catching this. It was my mistake, I forgot to > backport > > that change. It is a critical fix, so I think we should include it. > > > > Canceling this vote. I'll send a new candidate asap. > > > > On Thu, Jun 7, 2018 at 6:36 PM Masahiro Sakamoto > > > wrote: > > > > > Hi Matteo, > > > > > > It seems that the following modification has not been backported to > > > branch-2.0 yet. > > > https://github.com/apache/incubator-pulsar/pull/1893 > > > Is that okay with you? > > > > > > Regards, > > > > > > Masahiro > > > > > > > -Original Message- > > > > From: Matteo Merli [mailto:mme...@apache.org] > > > > Sent: Tuesday, June 05, 2018 2:44 PM > > > > To: dev@pulsar.incubator.apache.org > > > > Subject: [VOTE] Pulsar Release 2.0.1-incubating Candidate 1 > > > > > > > > This is the first release candidate for Apache Pulsar, version > > > > 2.0.1-incubating. > > > > > > > > This is a patch release that fixes few issues identified in previous > > > release > > > > 2.0.0-rc1-incubating. > > > > > > > > It fixes the following issues: > > > > https://github.com/apache/incubator-pulsar/milestone/14?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/incubator/pulsar/pulsar-2.0.1 > > > > -i > > > > ncubating-candidate-1/ > > > > > > > > SHA-1 checksums: > > > > > > > > ae1bd6f658ebff0745d5eb82961f400f9872f1da > > > > apache-pulsar-2.0.1-incubating-bin.tar.gz > > > > 2a22e40f290329ae5fac1d33e9754a67e01e882f > > > > apache-pulsar-2.0.1-incubating-src.tar.gz > > > > > > > > Maven staging repo: > > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1 > > > > 01 > > > > 9 > > > > > > > > The tag to be voted upon: > > > > v2.0.1-incubating-candidate-1 > > > > (b18a2689d592ac676ab70a5447cc023e378eda3b) > > > > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incub > > > > at > > > > ing-candidate-1 > > > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > > > > > Please download the the source package, and follow the README to > > > > build > > > and > > > > run the Pulsar standalone service. > > > > -- > > > > Matteo Merli > > > > > > > > > -- > > Matteo Merli > > > -- Matteo Merli
[CANCELED] Pulsar Release 2.0.1-incubating Candidate 1
Masahiro, thanks for catching this. It was my mistake, I forgot to backport that change. It is a critical fix, so I think we should include it. Canceling this vote. I'll send a new candidate asap. On Thu, Jun 7, 2018 at 6:36 PM Masahiro Sakamoto wrote: > Hi Matteo, > > It seems that the following modification has not been backported to > branch-2.0 yet. > https://github.com/apache/incubator-pulsar/pull/1893 > Is that okay with you? > > Regards, > > Masahiro > > > -Original Message- > > From: Matteo Merli [mailto:mme...@apache.org] > > Sent: Tuesday, June 05, 2018 2:44 PM > > To: dev@pulsar.incubator.apache.org > > Subject: [VOTE] Pulsar Release 2.0.1-incubating Candidate 1 > > > > This is the first release candidate for Apache Pulsar, version > > 2.0.1-incubating. > > > > This is a patch release that fixes few issues identified in previous > release > > 2.0.0-rc1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/14?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/incubator/pulsar/pulsar-2.0.1-i > > ncubating-candidate-1/ > > > > SHA-1 checksums: > > > > ae1bd6f658ebff0745d5eb82961f400f9872f1da > > apache-pulsar-2.0.1-incubating-bin.tar.gz > > 2a22e40f290329ae5fac1d33e9754a67e01e882f > > apache-pulsar-2.0.1-incubating-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-101 > > 9 > > > > The tag to be voted upon: > > v2.0.1-incubating-candidate-1 > > (b18a2689d592ac676ab70a5447cc023e378eda3b) > > https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incubat > > ing-candidate-1 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to build > and > > run the Pulsar standalone service. > > -- > > Matteo Merli > > > -- Matteo Merli
Re: [DISCUSSION] Podling name search
I also wanted to note that Yahoo legal and OSS department did conduct a rigorous validation process for the name, before open sourcing "Yahoo Pulsar" in Sept 2016. Of course that won't guarantee anything, but the name wasn't decided without putting some thought on it. Matteo On Thu, Jun 7, 2018 at 6:19 PM Matteo Merli wrote: > In my view, even if there were a 100% chance to be forced to change name > in 4 years, it would still make sense to change it then, rather than now. > > Changing it now, would mean to effectively kill the project, under any > plausible scenarios. > > Matteo > > On Thu, Jun 7, 2018 at 5:52 PM P. Taylor Goetz wrote: > >> I’d suggest thinking long and hard about this. Would you rather deal with >> a name change now, or 4 years from now as a TLP? >> >> It may sound like a remote possibility, but trust me, these things can >> and do happen. >> >> -Taylor >> >> >> >> > On Jun 7, 2018, at 8:01 PM, Matteo Merli wrote: >> > >> > As some in Pulsar community are already aware, one of the pending >> > tasks for Pulsar project to complete the "name search task". >> > >> > A JIRA task was opened to collect facts around usages of Pulsar >> > name: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-141 >> > >> > I had forwarded that to trademarks@ and this was the response >> > from Mark Thomas. >> > >> >> Pulsar is a very popular name for software. >> >> >> >> I don't see any obvious conflicts but given the popularity of the name >> >> it is likely, in a global marketplace, that there will be some. >> >> >> >> Should the project wish to register the "PULSAR" mark in the future, it >> >> is uncertain whether the ASF would be able to. Registering "APACHE >> >> PULSAR" is unlikely to hit any difficulties. >> >> >> >> It is more likely than usual that an infringement will emerge in the >> >> future that would require the project to rename. >> >> >> >> The podling needs to make a choice. Either: >> >> >> >> a) continue using PULSAR and accept that: >> >> - there are likely to be some restrictions on how the name is used >> >> (primarily that it always has to be APACHE PULSAR) >> >> - it is more likely than for most ASF projects that the project >> >> will be required to rename due to an infringement >> >> >> >> or >> >> >> >> b) pick a new name >> >> >> >> No rush on this. The podling should take time to discuss this. >> > >> > >> > Therefore we need to take a decision on this matter. >> > >> > My personal inclination is to continue to use "Apache Pulsar" and >> > have that to be registered as a trademark of ASF. >> > >> > My reasoning: >> > >> > * We are anyway already always referring to "Apache Pulsar" >> > rather than just "Pulsar" >> > >> > * Changing name at this point in life of the project would be >> > very disruptive. We just spent the past year into building >> > some naming awareness and it would all vanish, not to mention >> > the huge amount of work in updating documentation, package >> > names, etc. >> > >> > * If a conflict arise later on, it might be easier to change >> > name at that point. Once the project has a larger community >> > and bigger recognition, changing name would not mean to >> > restart from scratch. >> > >> > >> > I propose to have anyone share they thoughs on this issue. Once >> > there is a prevalent inclination in the community, we can vote a >> > final resolution on the subject. >> > >> > Thanks, >> > Matteo >> > >> > >> > >> > -- >> > Matteo Merli >> > >> > -- > Matteo Merli > > -- Matteo Merli
Re: [DISCUSSION] Podling name search
In my view, even if there were a 100% chance to be forced to change name in 4 years, it would still make sense to change it then, rather than now. Changing it now, would mean to effectively kill the project, under any plausible scenarios. Matteo On Thu, Jun 7, 2018 at 5:52 PM P. Taylor Goetz wrote: > I’d suggest thinking long and hard about this. Would you rather deal with > a name change now, or 4 years from now as a TLP? > > It may sound like a remote possibility, but trust me, these things can and > do happen. > > -Taylor > > > > > On Jun 7, 2018, at 8:01 PM, Matteo Merli wrote: > > > > As some in Pulsar community are already aware, one of the pending > > tasks for Pulsar project to complete the "name search task". > > > > A JIRA task was opened to collect facts around usages of Pulsar > > name: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-141 > > > > I had forwarded that to trademarks@ and this was the response > > from Mark Thomas. > > > >> Pulsar is a very popular name for software. > >> > >> I don't see any obvious conflicts but given the popularity of the name > >> it is likely, in a global marketplace, that there will be some. > >> > >> Should the project wish to register the "PULSAR" mark in the future, it > >> is uncertain whether the ASF would be able to. Registering "APACHE > >> PULSAR" is unlikely to hit any difficulties. > >> > >> It is more likely than usual that an infringement will emerge in the > >> future that would require the project to rename. > >> > >> The podling needs to make a choice. Either: > >> > >> a) continue using PULSAR and accept that: > >> - there are likely to be some restrictions on how the name is used > >> (primarily that it always has to be APACHE PULSAR) > >> - it is more likely than for most ASF projects that the project > >> will be required to rename due to an infringement > >> > >> or > >> > >> b) pick a new name > >> > >> No rush on this. The podling should take time to discuss this. > > > > > > Therefore we need to take a decision on this matter. > > > > My personal inclination is to continue to use "Apache Pulsar" and > > have that to be registered as a trademark of ASF. > > > > My reasoning: > > > > * We are anyway already always referring to "Apache Pulsar" > > rather than just "Pulsar" > > > > * Changing name at this point in life of the project would be > > very disruptive. We just spent the past year into building > > some naming awareness and it would all vanish, not to mention > > the huge amount of work in updating documentation, package > > names, etc. > > > > * If a conflict arise later on, it might be easier to change > > name at that point. Once the project has a larger community > > and bigger recognition, changing name would not mean to > > restart from scratch. > > > > > > I propose to have anyone share they thoughs on this issue. Once > > there is a prevalent inclination in the community, we can vote a > > final resolution on the subject. > > > > Thanks, > > Matteo > > > > > > > > -- > > Matteo Merli > > > -- Matteo Merli
[DISCUSSION] Podling name search
As some in Pulsar community are already aware, one of the pending tasks for Pulsar project to complete the "name search task". A JIRA task was opened to collect facts around usages of Pulsar name: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-141 I had forwarded that to trademarks@ and this was the response from Mark Thomas. > Pulsar is a very popular name for software. > > I don't see any obvious conflicts but given the popularity of the name > it is likely, in a global marketplace, that there will be some. > > Should the project wish to register the "PULSAR" mark in the future, it > is uncertain whether the ASF would be able to. Registering "APACHE > PULSAR" is unlikely to hit any difficulties. > > It is more likely than usual that an infringement will emerge in the > future that would require the project to rename. > > The podling needs to make a choice. Either: > > a) continue using PULSAR and accept that: >- there are likely to be some restrictions on how the name is used > (primarily that it always has to be APACHE PULSAR) >- it is more likely than for most ASF projects that the project > will be required to rename due to an infringement > > or > > b) pick a new name > > No rush on this. The podling should take time to discuss this. Therefore we need to take a decision on this matter. My personal inclination is to continue to use "Apache Pulsar" and have that to be registered as a trademark of ASF. My reasoning: * We are anyway already always referring to "Apache Pulsar" rather than just "Pulsar" * Changing name at this point in life of the project would be very disruptive. We just spent the past year into building some naming awareness and it would all vanish, not to mention the huge amount of work in updating documentation, package names, etc. * If a conflict arise later on, it might be easier to change name at that point. Once the project has a larger community and bigger recognition, changing name would not mean to restart from scratch. I propose to have anyone share they thoughs on this issue. Once there is a prevalent inclination in the community, we can vote a final resolution on the subject. Thanks, Matteo -- Matteo Merli
Re: Pulsar meetup in June/July
Joe, July 10th sounds good to me. Thank you for organizing. Hopefully many people from Pulsar community can attend. Matteo On Tue, Jun 5, 2018 at 11:21 AM Joe F wrote: > All, > > I got the availability for the venue in the 2nd week of July (50 people), > and its available on July 9th, 10th, or 13th . How does that sound? I > need to reserve a firm date... > > My preference is for 10th [since its not a Monday or Friday :-) ] but I'm > fine with a whatever is convenient for all .. > > > Joe > > On Sun, Jun 3, 2018 at 7:21 PM, Sijie Guo wrote: > > > Any updates? > > > > - Sijie > > > > On Mon, Apr 30, 2018 at 7:29 PM, Joe F wrote: > > > > > I would expect people to volunteer and sign up... that's why I said > > "from > > > Pulsar users and developers". > > > > > > > > > Joe > > > > > > On Mon, Apr 30, 2018 at 6:44 PM, Dave Fisher > > > wrote: > > > > > > > Hi - > > > > > > > > What would be the agenda? > > > > > > > > How can this event be promoted to help grow the community? > > > > > > > > Regards, > > > > Dave > > > > > > > > Sent from my iPhone > > > > > > > > > On Apr 30, 2018, at 11:29 AM, Joe F wrote: > > > > > > > > > > In June, it going to be a year since Pulsar was accepted into the > > > > incubator. > > > > > > > > > > I'm thinking of a meetup, with a few in-depth talks/presentations, > > > what's > > > > > new in Pulsar 2.0 etc, from Pulsar users and developers. Are > > people > > > > > interested in a 1/2day event? I can arrange for the venue and > > > > logistics. > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > -- Matteo Merli
Re: [DRAFT] Pulsar Podling report June 2018
Sure, me or whoever will volunteer for drafting the report will include that. Matteo On Thu, Jun 7, 2018 at 7:12 AM P. Taylor Goetz wrote: > Okay. Then please plan to include a discussion of progress made with > respect to brand management in your polling report for September. > > -Taylor > > > On Jun 7, 2018, at 1:03 AM, Matteo Merli wrote: > > > > Hi Taylor, > > > > The draft was obviously written before the issues were raised on the > > private list. I have already replied on the private@ list on the > specific > > and we'll continue to follow up there. I believe a reply in the report > > without the context of the questions would not be very helpful. > > > > Thanks, > > Matteo > > > > On Wed, Jun 6, 2018 at 9:26 PM P. Taylor Goetz <mailto:ptgo...@gmail.com>> wrote: > > > >> Thanks for sharing the report draft with dev@. It looks pretty good. > >> > >> As a mentor, I’d like to see some mention of how the pulsar PPMC plans > to > >> address the branding issues raised on private@. I feel pulsar is doing > >> very well in terms of releases, etc., but falling painfully short in > terms > >> of adhering to branding guidelines [1][2]. > >> > >> -Taylor > >> > >> [1] https://incubator.apache.org/guides/branding.html < > https://incubator.apache.org/guides/branding.html> < > >> https://incubator.apache.org/guides/branding.html < > https://incubator.apache.org/guides/branding.html>> > >> [2] https://www.apache.org/foundation/marks/pmcs < > https://www.apache.org/foundation/marks/pmcs> < > >> https://www.apache.org/foundation/marks/pmcs> > >> > >> > >>> On Jun 6, 2018, at 11:57 AM, Matteo Merli wrote: > >>> > >>> Here is the draft for the podling report. Please submit feedback soon, > >> the > >>> deadline is today (sorry for sending draft at last moment). > >>> > >>> > >>> > >>> > >>> 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 > >>> subscribers, and cross-datacenter replication. > >>> > >>> Pulsar has been incubating since 2017-06-01. > >>> > >>> Most important issues to address in the move towards graduation: > >>> > >>> 1. Complete the Podling name search tasks. The task is in progress > right > >>> now. > >>> > >>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > >> aware > >>> of? > >>> > >>> None > >>> > >>> How has the community developed since the last report? > >>> > >>> The community added 7 new contributors that submitted pull-requests > >> which > >>> were merged into master. > >>> > >>> The number of users approaching the team on the Slack channel has kept > >>> steadily increasing since the last report. Many users have actively > >>> deployed > >>> Pulsar for evaluation and production use cases. > >>> > >>> Project members from several companies have organized or participated > in > >>> several meetups, presenting Pulsar's introductions, deep-dives and > >>> hands-on > >>> tutorial, including recorded podcasts. We have several scheduled talks > >> on > >>> Pulsar at various conferences, 2 at ApacheCon in September, one at > OSCon > >>> in > >>> July and 2 others at Strata New York in September. A Pulsar dedicated > >>> meetup > >>> is being organized for next July. > >>> > >>> Since the last report the number of weekly-active-users on the Slack > >>> channel > >>> has increased from 53 to 88. > >>> > >>> We have reached the 1 year mark since Pulsar entering the Apache > >>> Incubator. > >>> Here is a summary of the community developments over the past year: > >>> > >>> > >>> 1. Pulsar community has done 5 Apache releases since entering > >>>incubator. The release process is well documented and we have > >>>had 4 different release managers from 3 different companies. > >>> > >>> 2. We have added 3
Re: [DRAFT] Pulsar Podling report June 2018
Hi Taylor, The draft was obviously written before the issues were raised on the private list. I have already replied on the private@ list on the specific and we'll continue to follow up there. I believe a reply in the report without the context of the questions would not be very helpful. Thanks, Matteo On Wed, Jun 6, 2018 at 9:26 PM P. Taylor Goetz wrote: > Thanks for sharing the report draft with dev@. It looks pretty good. > > As a mentor, I’d like to see some mention of how the pulsar PPMC plans to > address the branding issues raised on private@. I feel pulsar is doing > very well in terms of releases, etc., but falling painfully short in terms > of adhering to branding guidelines [1][2]. > > -Taylor > > [1] https://incubator.apache.org/guides/branding.html < > https://incubator.apache.org/guides/branding.html> > [2] https://www.apache.org/foundation/marks/pmcs < > https://www.apache.org/foundation/marks/pmcs> > > > > On Jun 6, 2018, at 11:57 AM, Matteo Merli wrote: > > > > Here is the draft for the podling report. Please submit feedback soon, > the > > deadline is today (sorry for sending draft at last moment). > > > > > > > > > > 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 > > subscribers, and cross-datacenter replication. > > > > Pulsar has been incubating since 2017-06-01. > > > > Most important issues to address in the move towards graduation: > > > > 1. Complete the Podling name search tasks. The task is in progress right > > now. > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware > > of? > > > > None > > > > How has the community developed since the last report? > > > > The community added 7 new contributors that submitted pull-requests > which > > were merged into master. > > > > The number of users approaching the team on the Slack channel has kept > > steadily increasing since the last report. Many users have actively > > deployed > > Pulsar for evaluation and production use cases. > > > > Project members from several companies have organized or participated in > > several meetups, presenting Pulsar's introductions, deep-dives and > > hands-on > > tutorial, including recorded podcasts. We have several scheduled talks > on > > Pulsar at various conferences, 2 at ApacheCon in September, one at OSCon > > in > > July and 2 others at Strata New York in September. A Pulsar dedicated > > meetup > > is being organized for next July. > > > > Since the last report the number of weekly-active-users on the Slack > > channel > > has increased from 53 to 88. > > > > We have reached the 1 year mark since Pulsar entering the Apache > > Incubator. > > Here is a summary of the community developments over the past year: > > > > > > 1. Pulsar community has done 5 Apache releases since entering > > incubator. The release process is well documented and we have > > had 4 different release managers from 3 different companies. > > > > 2. We have added 3 committers and PPMC members since incubation and > > there are also other candidates who have already made significant > > contributions to the project. > > > > 3. Community of users and people interested in Pulsar has expanded > > considerably. Thanks to the months long work in improving ease of > > use, documentation and blogs, many people became aware of Pulsar > > and started playing with it, then evaluating it and finally > > putting it in production for critical use cases. > > > > 4. We have tried to help users getting started through any > > communication channel. Even though we keep trying to encourage > > people to use the mailing list, most of the first interactions > > have been happening through the Slack channel. We also did make > > sure that: > > > > a) No decisions are taken in Slack channel > > > > b) Developers technical discussion happen mostly in Github > >issue/Pull-Request or in developers mailing list > > > > c) Conversations in Slack are sent to dev/user mailing list in a > >daily digest form for archival and to be searchable > > > > In any case Slack has been working fairly well in engaging with > > users, by providi
[DRAFT] Pulsar Podling report June 2018
into mainstream BookKeeper branch and released in BookKeeper 4.7.0, making possible for Pulsar to switch over from the Yahoo fork. 2. We have received a lot of feedback from people approaching Pulsar and learned a lot on how to simplify tools, documentation and concepts to make it easier for people to get started. 3. Based on the same feedback and inputs, we have been adding new features or extended existing features to match a new variety of use case, some of them outside the scope the initial Pulsar codebase from Yahoo. To summarize the "major" features added in the last year: - Pulsar stateless proxy - Non-persistent topics - End-to-End message encryption - Effectively-once semantics - Type-safe APIs - Schema Registry - Pulsar Functions - Topic compaction - Python client library With more scheduled for next upcoming release 2.1: - Pulsar IO connector framework - Tiered storage - Go client library 4. In addition to features, we have been trying to smooth the deployment of a production ready Pulsar cluster, by improving the documentation and providing templates for more common environments, such as Kubernetes, DCOS or just plain VMs with Ansible. 5. Having exposure to many users testing and using the sytem outside the original Yahoo use cases has proven very effecting in helping identifying and resolving corner cases that were not being stressed before. This resulted in a much resilient system that can adapt better to a large array of different requirements and environments. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2018-05-29, 2.0.0-rc1-incubating When were the last committers or PPMC members elected? 2018-05-28 - Jerry Peng 2018-05-28 - Sanjeev Kulkarni -- Matteo Merli
[VOTE] Pulsar Release 2.0.1-incubating Candidate 1
This is the first release candidate for Apache Pulsar, version 2.0.1-incubating. This is a patch release that fixes few issues identified in previous release 2.0.0-rc1-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/14?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/incubator/pulsar/pulsar-2.0.1-incubating-candidate-1/ SHA-1 checksums: ae1bd6f658ebff0745d5eb82961f400f9872f1da apache-pulsar-2.0.1-incubating-bin.tar.gz 2a22e40f290329ae5fac1d33e9754a67e01e882f apache-pulsar-2.0.1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1019 The tag to be voted upon: v2.0.1-incubating-candidate-1 (b18a2689d592ac676ab70a5447cc023e378eda3b) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incubating-candidate-1 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
Planning for patch release 2.0.1
Since we have released 2.0.0-rc1-incubating, a few issues were reported from users. Most of them are already being fixed. The list of fixes and PRs is at https://github.com/apache/incubator-pulsar/milestone/14 My intention would be to have a quick patch release that addresses all these issues in 2.0 and start the release process by next Monday, since few issues in packaging are preventing some features to work properly (proxy, Python client). Any thoughts? Any other changes that anyone feel should go in the patch release? Matteo -- Matteo Merli
Re: [VOTE] Pulsar Release 1.22.1-incubating Candidate 2
> Thanks Dave. I filed a github issue to take MD5 out of our website as well. The md5 signatures were already taken out (since 2.0) though the website still has a link to the non-existing md5 signatures On Fri, Jun 1, 2018 at 9:49 AM Sijie Guo wrote: > +1 (binding) > > Environment: MacOS 10.13.1 > > * check signatures, all are good. > * Bin distribution > - start standalone > - test producer/consumer using pulsar-client and pulsar-perf > * Src distribution > - compile and unit tests > - RAT check > - start standalone > - test producer/consumer using pulsar-client and pulsar-perf > > - Sijie > > On Fri, Jun 1, 2018 at 12:29 AM, Jai Asher wrote: > > > This is the second release candidate for Apache Pulsar, patch release > > version 1.22.1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/15?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/incubator/pulsar/ > > pulsar-1.22.1-incubating-candidate-2/ > > > > SHA-1 checksums: > > > > f2d29aa5e046c5bdefd8f466bce8e9ead80a2e09 > > apache-pulsar-1.22.1-incubating-src.tar.gz > > f2704cae22b7fb3c1b72daab6ebe7d484fdfec6b > > apache-pulsar-1.22.1-incubating-bin.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1018/ > > > > The tag to be voted upon: > > v1.22.1-incubating-candidate-1 (c9a369936af3b3ecc663b86ae959a3fbfa627aca) > > https://github.com/apache/incubator-pulsar/releases/tag/ > > v1.22.1-incubating-candidate-2 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the source package, and follow the README to build and > run > > the Pulsar standalone service. > > > -- Matteo Merli
[ANNOUNCE] Apache Pulsar 2.0.0-rc1-incubating released
The Apache Pulsar team is proud to announce Apache Pulsar version 2.0.0-rc1-incubating. This is the fifth Pulsar release after entering the Apache Incubator. 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 subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: https://pulsar.incubator.apache.org/download Release Notes are at: http://pulsar.apache.org/release-notes/#2.0.0-rc1-incubating We would like to thank the contributors that made the release possible. Regards, The Pulsar Team DISCLAIMER: Apache Pulsar is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. -- Matteo Merli
[RESULT] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5
The vote for releasing Apache Pulsar 2.0.0-rc1-incubating is now closed. With a total of +3 binding votes, +2 non binding votes and no -1 votes, the vote passes. +1s (binding): * Matteo Merli * Sijie Guo * Dave Fisher +1s (non-binding): * Jia Zhai * Ali Ahmed Thank you to all the reviewers for taking the time to validate this release. Matteo On Wed, May 23, 2018 at 12:53 AM Jia Zhai wrote: > +1 (non-binding) > > Environment: macOS 10.13.2 > > * asc, sha1, sha512 are good for both src and binary distributions > * binary distribution >- run standalone >- be able to produce and consume messages > * src distribution >- passed compile and all unit test. >- run standalone with compiled binary, be able to produce and consume. > > > On Wed, May 23, 2018 at 2:28 AM, Dave Fisher > wrote: > > > Hi - > > > > +1 (binding) > > > > $ mvn --version > > *Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; > > 2017-04-03T12:39:06-07:00)* > > Maven home: /Users/davewave/Development/apache-maven-3.5.0 > > Java version: 1.8.0_131, vendor: Oracle Corporation > > Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_ > > 131.jdk/Contents/Home/jre > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac" > > > > Checksums for bin and src both sha1 and sha512 are correct. > > Signature for both bin and src is Matteo. > > License, Notice, and Disclaimer files are present and look good. I’m ok > > with references into a licenses directory for the convenience binary. > > Built src following instructions in README.md. > > Please note that > > $ bin/pulsar standalone > > Fails if the base pulsar directory has been renamed after the build. The > > error is: > > Exception in thread "main" java.lang.NoClassDefFoundError: > > org/apache/pulsar/client/admin/PulsarAdminException > > at java.lang.Class.getDeclaredMethods0(Native Method) > > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) > > at java.lang.Class.privateGetMethodRecursive(Class.java:3048) > > at java.lang.Class.getMethod0(Class.java:3018) > > at java.lang.Class.getMethod(Class.java:1784) > > at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544) > > at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526) > > Caused by: java.lang.ClassNotFoundException: org.apache.pulsar.client. > > admin.PulsarAdminException > > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > > ... 7 more > > A quick scan of the commands did not reveal the trouble - the scripting > > looks good to me. > > > > Regards, > > Dave > > > > On May 20, 2018, at 6:23 PM, Matteo Merli wrote: > > > > This is the fifth release candidate for Apache Pulsar, version > > 2.0.0-rc1-incubating. > > > > The only difference from previous candidate is a fix on the LICENSE > > attached > > to bin distribution to correctly reflect all dependencies and versions. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ > > pulsar-2.0.0-rc1-incubating-candidate-5/ > > > > SHA-1 checksums: > > 72ee624c9b1485cc4c12b71e3807c7c05ec900ad > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > c525457db8f9c4ea859c595c93e9207631cda19f > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1017/ > > > > The tag to be voted upon: > > v2.0.0-rc1-incubating-candidate-5 (08708a198606fb934e46f6cb0b614f > > 2babf613e4) > > https://github.com/apache/incubator-pulsar/releases/tag/ > > v2.0.0-rc1-incubating-candidate-5 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to build > > and run the Pulsar standalone service. > > > > > > -- > > Matteo Merli > > > > > > > > > -- Matteo Merli
[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5
This is the fifth release candidate for Apache Pulsar, version 2.0.0-rc1-incubating. The only difference from previous candidate is a fix on the LICENSE attached to bin distribution to correctly reflect all dependencies and versions. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-5/ SHA-1 checksums: 72ee624c9b1485cc4c12b71e3807c7c05ec900ad apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz c525457db8f9c4ea859c595c93e9207631cda19f apache-pulsar-2.0.0-rc1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1017/ The tag to be voted upon: v2.0.0-rc1-incubating-candidate-5 (08708a198606fb934e46f6cb0b614f2babf613e4) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-5 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
[CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4
On Sun, May 20, 2018 at 5:32 PM Matteo Merli wrote: > Willem, thanks for catching these issues. > > I have fixed the missing dependencies, specified the exact version of each > of them > and added a script to validate that new changes won't break it later. > https://github.com/apache/incubator-pulsar/pull/1820 > > I will cancel this vote and create a new candidate. > > Matteo > > On Sat, May 19, 2018 at 11:12 PM Willem Jiang > wrote: > >> Hi, >> >> As there are some License issues in the binary distribution (please check >> the section4 for more information), I had to vote -1 (binding). >> >> Here are the verifications which I did >> 1. check the checksums and verify the KEY. >> These KEY are not signed by the others, so I got the warning WARNING: >> This key is not certified with a trusted signature! >> >> 2. Checked the License and Notice file of the source distribution. >> It looks good. >> >> 3. Built the source with instruction of README and start the server >> It works and I can start the standalone server. >> I also checked the distribution file in the all directory, I can get the >> binary and source distribution there. >> >> 4. Checked the License and Notice file of the binary distribution. >> There is not version of bundled jars specified in the License file. It >> could cause some trouble as the License could be changed in different >> versions of jar distribution. >> >> Most of the bundled jars are specified in the License file, but some of >> them are missed. >> >> * com.google.errorprone-error_prone_annotations-2.0.19.jar >> >> * com.google.instrumentation-instrumentation-api-0.4.3.jar >> >> * com.squareup.okhttp-okhttp-2.5.0.jar >> >> * com.squareup.okio-okio-1.6.0.jar >> >> * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar >> >> The javassist jar is not CDDL license, it has multiple licenses >> ASL,LGPL,MPL (we need to pick one of them). >> >> * org.javassist-javassist-3.21.0-GA.jar >> >> >> Willem Jiang >> >> >> On Fri, May 18, 2018 at 11:35 AM, Matteo Merli wrote: >> >> > This is the fourth release candidate for Apache Pulsar, version >> > 2.0.0-rc1-incubating. >> > >> > 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 subscribers, and >> geo-replication. >> > >> > Link to the voting thread on pulsar dev list: >> > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53 >> > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E >> > >> > It fixes the following issues: >> > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ >> > pulsar-2.0.0-rc1-incubating-candidate-4/ >> > >> > SHA-1 checksums: >> > a959a33500508d0ba690ca177eb39cf83dddf022 >> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz >> > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b >> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz >> > >> > Maven staging repo: >> > >> https://repository.apache.org/content/repositories/orgapachepulsar-1014/ >> > >> > The tag to be voted upon: >> > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f >> > 5eb4118de7) >> > https://github.com/apache/incubator-pulsar/releases/tag/ >> > v2.0.0-rc1-incubating-candidate-4 >> > >> > Pulsar's KEYS file containing PGP keys we use to sign the release: >> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS >> > >> > Please download the the source package, and follow the README to build >> > and run the Pulsar standalone service. >> > -- >> > Matteo Merli >> > >> > >> > -- > Matteo Merli > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4
Willem, thanks for catching these issues. I have fixed the missing dependencies, specified the exact version of each of them and added a script to validate that new changes won't break it later. https://github.com/apache/incubator-pulsar/pull/1820 I will cancel this vote and create a new candidate. Matteo On Sat, May 19, 2018 at 11:12 PM Willem Jiang wrote: > Hi, > > As there are some License issues in the binary distribution (please check > the section4 for more information), I had to vote -1 (binding). > > Here are the verifications which I did > 1. check the checksums and verify the KEY. > These KEY are not signed by the others, so I got the warning WARNING: > This key is not certified with a trusted signature! > > 2. Checked the License and Notice file of the source distribution. > It looks good. > > 3. Built the source with instruction of README and start the server > It works and I can start the standalone server. > I also checked the distribution file in the all directory, I can get the > binary and source distribution there. > > 4. Checked the License and Notice file of the binary distribution. > There is not version of bundled jars specified in the License file. It > could cause some trouble as the License could be changed in different > versions of jar distribution. > > Most of the bundled jars are specified in the License file, but some of > them are missed. > > * com.google.errorprone-error_prone_annotations-2.0.19.jar > > * com.google.instrumentation-instrumentation-api-0.4.3.jar > > * com.squareup.okhttp-okhttp-2.5.0.jar > > * com.squareup.okio-okio-1.6.0.jar > > * org.apache.distributedlog-distributedlog-core-shaded-4.7.0.jar > > The javassist jar is not CDDL license, it has multiple licenses > ASL,LGPL,MPL (we need to pick one of them). > > * org.javassist-javassist-3.21.0-GA.jar > > > Willem Jiang > > > On Fri, May 18, 2018 at 11:35 AM, Matteo Merli wrote: > > > This is the fourth release candidate for Apache Pulsar, version > > 2.0.0-rc1-incubating. > > > > 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 subscribers, and > geo-replication. > > > > Link to the voting thread on pulsar dev list: > > https://lists.apache.org/thread.html/865ac7e993265a31512642c5f29e53 > > e65f4199b931a5ae91d07fba77@%3Cdev.pulsar.apache.org%3E > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ > > pulsar-2.0.0-rc1-incubating-candidate-4/ > > > > SHA-1 checksums: > > a959a33500508d0ba690ca177eb39cf83dddf022 > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1014/ > > > > The tag to be voted upon: > > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f > > 5eb4118de7) > > https://github.com/apache/incubator-pulsar/releases/tag/ > > v2.0.0-rc1-incubating-candidate-4 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to build > > and run the Pulsar standalone service. > > -- > > Matteo Merli > > > > > -- Matteo Merli
Re: [VOTE] Pulsar Release 1.22.1-incubating Candidate 1
Jai, I think we should also include this fix: https://github.com/apache/incubator-pulsar/pull/1817 On Tue, May 15, 2018 at 9:25 PM Jai Asher wrote: > This is the first release candidate for Apache Pulsar, patch release > version 1.22.1-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/15?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/incubator/pulsar/pulsar-1.22.1-incubating-candidate-1/ > > SHA-1 checksums: > 242dd7772acae4bce0f30a6f9be51cb65864f560 > apache-pulsar-1.22.1-incubating-bin.tar.gz > c5cf3ef97fde5f8ac613f2a886c3b1379d8bf27d > apache-pulsar-1.22.1-incubating-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1016/ > > The tag to be voted upon: > v1.22.1-incubating-candidate-1 (0093a8024f2be1aea8d85406dca403c3ef01e17c) > > https://github.com/apache/incubator-pulsar/releases/tag/v1.22.1-incubating-candidate-1 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > -- Matteo Merli
[RESULT] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4
The vote for releasing Apache Pulsar 2.0.0-rc1-incubating is now closed. With a total of +4 binding votes, +2 non binding votes and no -1 votes, the vote passes. +1s (binding): * Matteo Merli * Sijie Guo * Rajan Dhabalia * Nozomi Kurihara +1s (non-binding): * Jia Zhai * Jerry Peng Thank you to all the reviewers for taking the time to validate this release. Matteo On Wed, May 16, 2018 at 5:16 PM Nozomi Kurihara wrote: > +1 (binding) > > Environment: MacOS 10.13.4 > > * check sha1, sha512, asc > * Bin distribution > - start standalone > - producer/consumer worked > - pulsar-functions worked > * Src distribution > - compile and unit tests > - RAT check > - start standalone > - producer/consumer worked > - pulsar-functions worked > > Regards, > Nozomi > > > > 差出人: Jia Zhai > 送信日時: 2018年5月16日 11:10:01 > 宛先: dev@pulsar.incubator.apache.org > 件名: Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4 > > +1 (non-binding) > > Environment: macOS 10.13.2 > > * asc, sha1, sha512 are good for both src and binary distributions > * binary distribution >- run standalone >- be able to produce and consume messages > * src distribution >- passed compile and all unit test. >- run standalone with compiled binary, be able to produce and consume. > > On Wed, May 16, 2018 at 9:40 AM, Rajan Dhabalia > wrote: > > > +1 (binding) > > > > Environment: Mac-OS 10.12.6 > > > > Checked: > > - signatures and checksum > > - maven repository artifacts > > - start standalone service and client-test for producer/consumer > (src/bin > > distribution) > > - rat check on src distribution > > - compile and unit test on src distribution > > > > Thanks, > > Rajan > > > > On Mon, May 14, 2018 at 4:33 PM, Matteo Merli wrote: > > > > > This is the fourth release candidate for Apache Pulsar, version > > > 2.0.0-rc1-incubating. > > > > > > It fixes the following issues: > > > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ > > > pulsar-2.0.0-rc1-incubating-candidate-4/ > > > > > > SHA-1 checksums: > > > a959a33500508d0ba690ca177eb39cf83dddf022 > > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b > > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > > > Maven staging repo: > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1014/ > > > > > > The tag to be voted upon: > > > v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f > > > 5eb4118de7) > > > https://github.com/apache/incubator-pulsar/releases/tag/ > > > v2.0.0-rc1-incubating-candidate-4 > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > > > Please download the the source package, and follow the README to build > > > and run the Pulsar standalone service. > > > > > > -- > > > Matteo Merli > > > > > > > > > -- Matteo Merli
Re: [VOTE][DISCUSS] Pulsar Release 2.0.0-rc1-incubating Candidate 4
Hi Dave, the main problem in building the jar as part of build is that we need to have the Jar built by Maven before the test of that module are executed, though the Jar itself doesn't have to be in the classpath, otherwise the test verification is not useful. The test itself was loading a jar and verifying the class was loaded. We have tried a few variations in Maven to get it working but with no luck, so concluded it was better to move on for now without that test. Testing the loading of the Jar is something that could probably be done more easily as part of integration tests anyway. Ivan has recently done a lot of work to include the integration testing framework. We should be able to add some tests there to verify this functionality. Matteo On Tue, May 15, 2018 at 4:21 PM Dave Fisher wrote: > Hi - > > Perhaps I missed the discussion about the Jar file. It looks like the > decision was made to eliminate the test. > > I think that a better approach would be to actually compile it as part of > the build. This would allow the test to also serve as a sort of “Hello > World” for Pulsar functions. > > Is this the plan for 2.1? > > Regards, > Dave > > > > On May 14, 2018, at 4:33 PM, Matteo Merli wrote: > > > > This is the fourth release candidate for Apache Pulsar, version > > 2.0.0-rc1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-4/ > > > > SHA-1 checksums: > > a959a33500508d0ba690ca177eb39cf83dddf022 > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1014/ > > > > The tag to be voted upon: > > v2.0.0-rc1-incubating-candidate-4 > (e5d3bda9607703c2e012983c7ef64f5eb4118de7) > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-4 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to build > > and run the Pulsar standalone service. > > > > -- > > Matteo Merli > > > > -- Matteo Merli
[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 4
This is the fourth release candidate for Apache Pulsar, version 2.0.0-rc1-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-4/ SHA-1 checksums: a959a33500508d0ba690ca177eb39cf83dddf022 apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz 5b9bedd2f284c5a8d95ba6dc3c70af8c266fbb3b apache-pulsar-2.0.0-rc1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1014/ The tag to be voted upon: v2.0.0-rc1-incubating-candidate-4 (e5d3bda9607703c2e012983c7ef64f5eb4118de7) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-4 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
[CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3
Canceling this vote thread to remove pre-packaged jar used in unit tests. Matteo On Sat, May 12, 2018 at 7:18 PM Dave Fisher wrote: > Hi Pulsar Devs, > > Thanks Justin! I know that Pulsar Functions are new. > > $ jar tvf > apache-pulsar-2.0.0-rc1-incubating/pulsar-functions/utils/src/test/resources/multifunction.jar > 0 Wed Dec 13 01:00:28 PST 2017 META-INF/ >147 Wed Dec 13 01:00:28 PST 2017 META-INF/MANIFEST.MF > 0 Wed Dec 13 00:58:36 PST 2017 org/ > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/ > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/ > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/ > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/runtime/ > 0 Wed Dec 13 00:58:56 PST 2017 > org/apache/pulsar/functions/runtime/functioncache/ >683 Wed Dec 13 00:57:10 PST 2017 > org/apache/pulsar/functions/runtime/functioncache/AddFunction.class > > AddFunction is nowhere in the source. This is something that must be > corrected. > > Sorry, but I am going to change my votes to +0 until there is an > explanation. One option would be to remove this test … > > Please keep the eye out for jars and tars in the source. > > Regards, > Dave > > On May 12, 2018, at 3:52 PM, Justin Mclean > wrote: > > Hi, > > Sorry but it’s -1 binding due to compiled code in source release. > > Frankly I’m surprised to see so many +1s with this obvious issue. > > I checked: > - incubating in name > - signatures and hashes correct > - DISCLAIMER exists > - LICENSE and NOTICE good > - Unexpected jar in source release [1] > - All source files have headers > > Thanks, > Justin > > > 1. pulsar-functions/utils/src/test/resources/multifunction.jar > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3
Hi Matt, can you expand a bit more on the issue, because I'm not 100% sure I understand it correctly. > -1 as well. For strange build requirements that need to inject class files, that would still only be applied to the binary artifacts The code in question is testing a feature that takes Jars from a user and execute the code contained. Indeed the Jar should not be in the sources, though I believe the test is correct here: we need to validate the specific feature by dynamically loading a Jar. > (e.g., injecting a module-info.class file at build time rather than requiring Java 9+ to build regardless). I don't see any place in the code where we are using "module-info.class" and the project requires Java 8 and not 9. Thanks, Matteo On Sun, May 13, 2018 at 8:46 AM Matt Sicker wrote: > -1 as well. For strange build requirements that need to inject class files, > that would still only be applied to the binary artifacts (e.g., injecting a > module-info.class file at build time rather than requiring Java 9+ to build > regardless). > > On 12 May 2018 at 21:17, Dave Fisher wrote: > > > Hi Pulsar Devs, > > > > Thanks Justin! I know that Pulsar Functions are new. > > > > $ jar tvf apache-pulsar-2.0.0-rc1-incubating/pulsar-functions/ > > utils/src/test/resources/multifunction.jar > > 0 Wed Dec 13 01:00:28 PST 2017 META-INF/ > >147 Wed Dec 13 01:00:28 PST 2017 META-INF/MANIFEST.MF > > 0 Wed Dec 13 00:58:36 PST 2017 org/ > > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/ > > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/ > > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/ > > 0 Wed Dec 13 00:58:36 PST 2017 org/apache/pulsar/functions/runtime/ > > 0 Wed Dec 13 00:58:56 PST 2017 org/apache/pulsar/functions/ > > runtime/functioncache/ > >683 Wed Dec 13 00:57:10 PST 2017 org/apache/pulsar/functions/ > > runtime/functioncache/AddFunction.class > > > > AddFunction is nowhere in the source. This is something that must be > > corrected. > > > > Sorry, but I am going to change my votes to +0 until there is an > > explanation. One option would be to remove this test … > > > > Please keep the eye out for jars and tars in the source. > > > > Regards, > > Dave > > > > On May 12, 2018, at 3:52 PM, Justin Mclean > > wrote: > > > > Hi, > > > > Sorry but it’s -1 binding due to compiled code in source release. > > > > Frankly I’m surprised to see so many +1s with this obvious issue. > > > > I checked: > > - incubating in name > > - signatures and hashes correct > > - DISCLAIMER exists > > - LICENSE and NOTICE good > > - Unexpected jar in source release [1] > > - All source files have headers > > > > Thanks, > > Justin > > > > > > 1. pulsar-functions/utils/src/test/resources/multifunction.jar > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- > Matt Sicker > -- Matteo Merli
[RESULT] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3
The vote for releasing Apache Pulsar 2.0.0-rc1-incubating is now closed. With a total of +6 binding votes, +3 non binding votes and no -1 votes, the vote passes. +1s (binding): * Sijie Guo * Jim Jagielski * P. Taylor Goetz * Rajan Dhabalia * Nozomi Kurihara * Dave Fisher +1s (non-binding): * Jia Zhai * David Rusek * Ivan Kelly Thank you to all the reviewers for taking the time to validate this release. Matteo On Fri, May 11, 2018 at 3:08 AM Ivan Kelly wrote: > +1 (non-binding) > > - Signatures and hashes are good > - LICENSEs and NOTICEs are good > - Rat and tests are clean (some env issues locally, but fine on a clean VM) > - nit: the source distribution is missing the dockerfile and scripts > to build the testing docker image, so I couldn't run integration tests > from the source package. Can run by checking out the branch though. > Clean > - Set up a small multi cluster, pubsub works fine with replication > - I couldn't get functions to work. On-cluster hung when uploading the > py file. localrun didn't work at all with python (packages missing). > localrun starts with a java jar, but didn't write anything to output > topic. > > -Ivan > > > > On Wed, May 9, 2018 at 12:22 AM, Matteo Merli wrote: > > This is the third release candidate for Apache Pulsar, version > > 2.0.0-rc1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-3/ > > > > SHA-1 checksums: > > b1a392c5935448da195eb927520fe6deb20182fc > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > 8c547a3e0afaee3446c770c076d5803e7e7da1c2 > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1013/ > > > > The tag to be voted upon: > > v2.0.0-rc1-incubating-candidate-3 > (9b33a8788f171f98528aeaa9040d16fc702404ef) > > > https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to build > > and run the Pulsar standalone service. > > -- > > Matteo Merli > > > -- Matteo Merli
Pulsar Go client library
Hi all, I've created a PR to add the Go client library for Pulsar. https://github.com/apache/incubator-pulsar/pull/1764 It would be nice to have this reviewed by a number of Go developers to gather feedback. This is the first piece of Go code I wrote.. so that's likely to violate a number of best practices :) Ultimately, the library and the API needs to make sense and feel natural to Go developers. Matteo -- Matteo Merli
Planning for Pulsar 2.1 release
Now that 2.0 is on the way, I'd like to get some items that we're targeting to get into a 2.1 release: * Connector framework (pulsar-io), built on top of Pulsar Functions * Go client library (based on C++ Pulsar client lib) * Tooling and docs around rack-aware deployment * Tiered storage framework (with S3 as first supported backend) * Schema integration for unctions * Distributed state in functions * Avro schema support * Improvements in pulsar-admin cli tool The idea would be to have a 2.1 release in early June. What are the thoughts around this? Matteo -- Matteo Merli
[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3
This is the third release candidate for Apache Pulsar, version 2.0.0-rc1-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-3/ SHA-1 checksums: b1a392c5935448da195eb927520fe6deb20182fc apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz 8c547a3e0afaee3446c770c076d5803e7e7da1c2 apache-pulsar-2.0.0-rc1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1013/ The tag to be voted upon: v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2
Adding the Netty deps licenses, but I don't think we need to report the ASL license in our NOTICE. The license for Netty is anyway reported in our LICENSE file. On Tue, May 8, 2018 at 10:24 AM Ivan Kelly wrote: > > Created PR at https://github.com/apache/incubator-pulsar/pull/1748 > > I'll take a look, but it may be tomorrow before I get the time. > > > In some cases, the feedback for the NOTICE file has been to avoid > inclusion > > on what was not strictly required, in particular, regarding non ASL > > licensed projects. Another example was around Netty NOTICE file which was > > originally bubbled up and then we removed it after feedback. > > Netty is a strange case, because they put far too much in their notice > file. However, if there is something in the netty notice file which > refers to ASLv2 code which has been included in the netty source, and > a binary object based on that code is shipped with pulsar, then that > should be bubbled up from the netty code. As far as I can tell (and > assuming the case is the same as for bookkeeper), the part of the > netty notice which should be bubbled up to pulsar notice is: > > > The Netty Project > = > > Please visit the Netty web site for more information: > > * http://netty.io/ > > Copyright 2014 The Netty Project > > The Netty Project licenses this file to you under the Apache License, > version 2.0 (the "License"); you may not use this file except in compliance > with the License. You may obtain a copy of the License at: > > http://www.apache.org/licenses/LICENSE-2.0 > > Unless required by applicable law or agreed to in writing, software > distributed under the License is distributed on an "AS IS" BASIS, WITHOUT > WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the > License for the specific language governing permissions and limitations > under the License. > > > There is other code, which netty integrates into its code, but which > is MIT/BSD license. These should be notes in the LICENSE. > See > https://github.com/apache/bookkeeper/blob/master/bookkeeper-dist/src/main/resources/LICENSE-all.bin.txt#L368-L416 > > -Ivan > -- Matteo Merli
[CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2
Canceling vote to include license and notice fixes. On Tue, May 8, 2018 at 9:56 AM Matteo Merli wrote: > Thanks for checking thouroughly. > > Created PR at https://github.com/apache/incubator-pulsar/pull/1748 > > In some cases, the feedback for the NOTICE file has been to avoid > inclusion on what was not strictly required, in particular, regarding non > ASL licensed projects. Another example was around Netty NOTICE file which > was originally bubbled up and then we removed it after feedback. > > Matteo > > > On Tue, May 8, 2018 at 8:08 AM Ivan Kelly wrote: > >> -1 >> >> There's quite a few issues with LICENSE and NOTICE >> >> >> https://gist.githubusercontent.com/ivankelly/a93f06d2a3075575c43a0dd44165bac1/raw/83551daf958432f532ee53cccaa6397f0c1af7bf/pulsar-libs.org >> >> Some stuff is missing completely. Others are incomplete. >> >> Note that this only applies to the binary distribution. The source is >> fine in this regard. >> > -- > Matteo Merli > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2
Thanks for checking thouroughly. Created PR at https://github.com/apache/incubator-pulsar/pull/1748 In some cases, the feedback for the NOTICE file has been to avoid inclusion on what was not strictly required, in particular, regarding non ASL licensed projects. Another example was around Netty NOTICE file which was originally bubbled up and then we removed it after feedback. Matteo On Tue, May 8, 2018 at 8:08 AM Ivan Kelly wrote: > -1 > > There's quite a few issues with LICENSE and NOTICE > > > https://gist.githubusercontent.com/ivankelly/a93f06d2a3075575c43a0dd44165bac1/raw/83551daf958432f532ee53cccaa6397f0c1af7bf/pulsar-libs.org > > Some stuff is missing completely. Others are incomplete. > > Note that this only applies to the binary distribution. The source is > fine in this regard. > -- Matteo Merli
Re: Embedded pulsar cluster?
Hi Jun,
there are few options:
1. We have a MockedBrokerService that we use in our unit tests. It's not
super-fancy but it might work:
https://github.com/apache/incubator-pulsar/blob/master/pulsar-broker/src/test/java/org/apache/pulsar/broker/auth/MockedPulsarServiceBaseTest.java
That starts a "real" broker instance with mocked ZooKeeper and
BookKeeper to keep data in memory. The way we typically use this is by
extending from that class and create tests.
2. There is a standalone Pulsar service ("bin/pulsar standalone") that
includes broker, ZK and BK service in a single JVM process. It uses the
"real" implementation of each component and stores the data on disk. It was
not initially meant to be embedded but it might actually very easy to fix.
3. There's a LocalBookkeeperEnsemble class that creates a ZK + BK service
and, combined with a PulsarService instance, could get the whole service
up. I agree that a single class "service" would be a nicer option.
Matteo
On Fri, May 4, 2018 at 12:55 PM jun aoki wrote:
> do you guys have embedded pulsar I can use for unit tests?
> Something similar embedded kafka to
>
> https://github.com/apache/kafka/blob/trunk/streams/src/test/java/org/apache/kafka/streams/integration/utils/EmbeddedKafkaCluster.java
>
> I'd like to play with pulsar by replacing our kafka stream app with it.
>
> --
> -jun
>
--
Matteo Merli
[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 2
This is the second release candidate for Apache Pulsar, version 2.0.0-rc1-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-2/ SHA-1 checksums: ea3e2fbbc4abbb2b785a8ff49542d26fb5225323 apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz fe22b1f143f9cb347ecfabc06df440d5585eb90b apache-pulsar-2.0.0-rc1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1012/ The tag to be voted upon: v2.0.0-rc1-incubating-candidate-2 (ea1230aef81d68ac98edeee188439b350d4cadc0) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-2 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 1
On Thu, May 3, 2018 at 3:21 PM P. Taylor Goetz wrote: > Hi Matteo, > > When you cancel a VOTE, you should replace the “Re:” in the subject line > with “[CANCELED]”. IIRC, there is some ASF tooling that looks for that. > Thanks, noted and replied. > > A few other things: > > - The release artifacts should be prefixed with “apache-pulsar” > - The checksum and signature files should be included in the dist > directory, and referenced in the vote email. > - If you have Maven artifacts, link to the Nexus staging repository. > I think all these items should be already in order. I have removed the dist directory for the 1st candidate as I pushed candidate-2, so that's why you might not have the chance to check. I'm starting next vote thread in a few minutes. > - Your first release will likely be a the hardest. Be patient. ;) > I will, though it's not my first release ;) Thanks, Matteo -- Matteo Merli
Re: [CANCELED] [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 1
On Thu, May 3, 2018 at 2:24 PM Matteo Merli wrote: > Closing this. I'm preparing candidate 2 > > > On Thu, May 3, 2018 at 12:37 PM Matteo Merli > wrote: > >> Good find. I will send a new release candidate with this fix in a few >> hours. In the meantime please still validate this candidate so that we can >> spot issues before "candidate 2" >> >> Matteo >> >> On Thu, May 3, 2018 at 12:23 PM Sijie Guo wrote: >> >>> Sorry. I have to put -1 here. >>> >>> source/binary distributions looks good (asc, sha1, sha512). pub/sub >>> functionalities are good on both src and binary distribution, verified >>> via >>> standalone, pulsar-client and pulsar-perf >>> release tag, artifacts are good as well. >>> >>> however I think functions is broken with the binary distribution, due >>> assembly plugin includes unshaded dependencies. putting a fix up for it. >>> >>> - Sijie >>> >>> On Wed, May 2, 2018 at 12:16 AM, Matteo Merli wrote: >>> >>> > This is the first release candidate for Apache Pulsar, version >>> > 2.0.0-rc1-incubating. >>> > >>> > It fixes the following issues: >>> > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ >>> > pulsar-2.0.0-rc1-incubating-candidate-1/ >>> > >>> > SHA-1 checksums: >>> > >>> > 0054815ecfde558ce730259b1a1b3c40dfecb727 >>> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz >>> > bffefb8f6ef67bf9ad0d26f706a098ff000deb3d >>> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz >>> > >>> > Maven staging repo: >>> > >>> https://repository.apache.org/content/repositories/orgapachepulsar-1011/ >>> > >>> > The tag to be voted upon: >>> > v2.0.0-rc1-incubating-candidate-1 (60869dd69e2a99d835b44042171633 >>> > 9b145e9c70) >>> > https://github.com/apache/incubator-pulsar/releases/tag/ >>> > v2.0.0-rc1-incubating-candidate-1 >>> > >>> > Pulsar's KEYS file containing PGP keys we use to sign the release: >>> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS >>> > >>> > Please download the the source package, and follow the README to build >>> > and run the Pulsar standalone service. >>> > -- >>> > Matteo Merli >>> > >>> > >>> >> -- >> Matteo Merli >> >> > -- > Matteo Merli > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 1
Closing this. I'm preparing candidate 2 On Thu, May 3, 2018 at 12:37 PM Matteo Merli wrote: > Good find. I will send a new release candidate with this fix in a few > hours. In the meantime please still validate this candidate so that we can > spot issues before "candidate 2" > > Matteo > > On Thu, May 3, 2018 at 12:23 PM Sijie Guo wrote: > >> Sorry. I have to put -1 here. >> >> source/binary distributions looks good (asc, sha1, sha512). pub/sub >> functionalities are good on both src and binary distribution, verified via >> standalone, pulsar-client and pulsar-perf >> release tag, artifacts are good as well. >> >> however I think functions is broken with the binary distribution, due >> assembly plugin includes unshaded dependencies. putting a fix up for it. >> >> - Sijie >> >> On Wed, May 2, 2018 at 12:16 AM, Matteo Merli wrote: >> >> > This is the first release candidate for Apache Pulsar, version >> > 2.0.0-rc1-incubating. >> > >> > It fixes the following issues: >> > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ >> > pulsar-2.0.0-rc1-incubating-candidate-1/ >> > >> > SHA-1 checksums: >> > >> > 0054815ecfde558ce730259b1a1b3c40dfecb727 >> > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz >> > bffefb8f6ef67bf9ad0d26f706a098ff000deb3d >> > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz >> > >> > Maven staging repo: >> > >> https://repository.apache.org/content/repositories/orgapachepulsar-1011/ >> > >> > The tag to be voted upon: >> > v2.0.0-rc1-incubating-candidate-1 (60869dd69e2a99d835b44042171633 >> > 9b145e9c70) >> > https://github.com/apache/incubator-pulsar/releases/tag/ >> > v2.0.0-rc1-incubating-candidate-1 >> > >> > Pulsar's KEYS file containing PGP keys we use to sign the release: >> > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS >> > >> > Please download the the source package, and follow the README to build >> > and run the Pulsar standalone service. >> > -- >> > Matteo Merli >> > >> > >> > -- > Matteo Merli > > -- Matteo Merli
Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 1
Good find. I will send a new release candidate with this fix in a few hours. In the meantime please still validate this candidate so that we can spot issues before "candidate 2" Matteo On Thu, May 3, 2018 at 12:23 PM Sijie Guo wrote: > Sorry. I have to put -1 here. > > source/binary distributions looks good (asc, sha1, sha512). pub/sub > functionalities are good on both src and binary distribution, verified via > standalone, pulsar-client and pulsar-perf > release tag, artifacts are good as well. > > however I think functions is broken with the binary distribution, due > assembly plugin includes unshaded dependencies. putting a fix up for it. > > - Sijie > > On Wed, May 2, 2018 at 12:16 AM, Matteo Merli wrote: > > > This is the first release candidate for Apache Pulsar, version > > 2.0.0-rc1-incubating. > > > > It fixes the following issues: > > https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/ > > pulsar-2.0.0-rc1-incubating-candidate-1/ > > > > SHA-1 checksums: > > > > 0054815ecfde558ce730259b1a1b3c40dfecb727 > > apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz > > bffefb8f6ef67bf9ad0d26f706a098ff000deb3d > > apache-pulsar-2.0.0-rc1-incubating-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1011/ > > > > The tag to be voted upon: > > v2.0.0-rc1-incubating-candidate-1 (60869dd69e2a99d835b44042171633 > > 9b145e9c70) > > https://github.com/apache/incubator-pulsar/releases/tag/ > > v2.0.0-rc1-incubating-candidate-1 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > Please download the the source package, and follow the README to build > > and run the Pulsar standalone service. > > -- > > Matteo Merli > > > > > -- Matteo Merli
[VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 1
This is the first release candidate for Apache Pulsar, version 2.0.0-rc1-incubating. It fixes the following issues: https://github.com/apache/incubator-pulsar/milestone/12?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/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-1/ SHA-1 checksums: 0054815ecfde558ce730259b1a1b3c40dfecb727 apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz bffefb8f6ef67bf9ad0d26f706a098ff000deb3d apache-pulsar-2.0.0-rc1-incubating-src.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1011/ The tag to be voted upon: v2.0.0-rc1-incubating-candidate-1 (60869dd69e2a99d835b440421716339b145e9c70) https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-1 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS Please download the the source package, and follow the README to build and run the Pulsar standalone service. -- Matteo Merli
Re: Plan for Pulsar 2.0 release
I think we're getting closer to the release. Most of the changes marked for 2.0.0 were already merged, there are few tasks on the documentation side that are getting closed as well. https://github.com/apache/incubator-pulsar/milestone/12 If there's something that really needs to be added / fixed prior to the release, please raise your hand. Otherwise, once the pending tasks are done, I'll start the release process for 2.0.0-rc1. Matteo On Thu, Apr 19, 2018 at 10:14 AM Ivan Kelly wrote: > On Thu, Apr 19, 2018 at 10:07 AM, Dave Fisher > wrote: > > Is it possible to have 2.0.0alpha on a Maven Central release?> > > Zookeeper do it all the time. > > http://search.maven.org/#artifactdetails%7Corg.apache.zookeeper%7Czookeeper%7C3.5.3-beta%7Cpom > > -Ivan > -- Matteo Merli
Re: minor/bugfix release
> Since I was responsible for releasing 1.22, I don't mind taking up this task. Good, let's try to compile a list of commits with fixes that need to be backported into 1.22.1 from master. Jai, since the PRs can only have 1 milestone associated, we should use a different way to mark them, perhaps with a github project. On Thu, Apr 19, 2018 at 11:54 AM Sahaya Andrews wrote: > Agree. > > I can also take up the release task. > > On Thu, Apr 19, 2018 at 11:42 AM, Jai Asher wrote: > > +1 to 1.22.1 release - I think a bug fix (patch) release is a great idea > > especially if we have user-facing bugs. Since I was responsible for > > releasing 1.22, I don't mind taking up this task. > > > > > > On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo wrote: > > > >> Hi all, > >> > >> I think there are a couple of bugs reported on 1.22.0 when users are > using > >> it. Shall we consider doing a 1.22.1 release? > >> > >> - Sijie > >> > >> On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo wrote: > >> > >> > Hi all, > >> > > >> > Currently pulsar release schedule is mainly on feature releases. Any > idea > >> > on bugfix releases? > >> > > >> > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1 > >> > release with bug fixes? > >> > > >> > Thoughts? > >> > > >> > - Sijie > >> > > >> > > >> > -- Matteo Merli
Re: Plan for Pulsar 2.0 release
Yes, the 1.x client can be used with a 2.x broker and vice-versa. Also it has been tested the upgrade and rollback scenario. Eg: live upgrade a cluster to 2.0 and rollback to 1.22 in case of any unexpected problem. It would be nice to automate this tests with the integration framework that Ivan has added. On Fri, Apr 13, 2018 at 9:50 AM Joe F wrote: > Is client API compatibility and upgrade procedure working with the previous > version? > > Joe > > > On Fri, Apr 13, 2018 at 9:27 AM, Matteo Merli wrote: > > > Hi everyone, > > > > I think we are approaching the completion of most major items that were > > scheduled for 2.0 release. > > > > Since there is a big number of items that went in, like for example: > > * Migrating BookKeeper from Yahoo branch based on 4.3 to main Apache 4.7 > > * Schema > > * Topic Compaction > > * Functions > > * Client API refactorings > > > > I would suggest to have a "2.0.0-RC1" release, still officially released > > with regular process, so that we'll have a chance to iron out any bugs, > > tools or packaging issue before marking 2.0 as "stable". > > > > My idea is use next week to finish up all the pending tasks and > > documentation changes and kickoff the release process for 2.0.0-rc1 in > the > > week after. > > > > Any thoughts with respect to this? > > > > Matteo > > -- > > Matteo Merli > > > > > -- Matteo Merli
Plan for Pulsar 2.0 release
Hi everyone, I think we are approaching the completion of most major items that were scheduled for 2.0 release. Since there is a big number of items that went in, like for example: * Migrating BookKeeper from Yahoo branch based on 4.3 to main Apache 4.7 * Schema * Topic Compaction * Functions * Client API refactorings I would suggest to have a "2.0.0-RC1" release, still officially released with regular process, so that we'll have a chance to iron out any bugs, tools or packaging issue before marking 2.0 as "stable". My idea is use next week to finish up all the pending tasks and documentation changes and kickoff the release process for 2.0.0-rc1 in the week after. Any thoughts with respect to this? Matteo -- Matteo Merli
Re: PIP review process - improvement
Sounds good. We can move the wiki pages content into same git repo and maybe just keep index with links in wiki. On Mon, Apr 9, 2018 at 1:35 AM Ivan Kelly wrote: > > It will keep the discussion public, convenient, archived, maintain > history, > > and will be mailed out (with github notifications). > > > > What do you all say? > > +1 for this. This is how BK does it, and I've found it much easier to use. > > -Ivan > -- Matteo Merli
Re: [DISCUSS] PIP-16: Tiered storage
Added to Wiki as well at : https://github.com/apache/incubator-pulsar/wiki/PIP-17:-Tiered-storage-for-Pulsar-topics On Thu, Apr 5, 2018 at 8:52 AM Ivan Kelly wrote: > Hi folks, > > This proposal is to add tiered storage to pulsar. > > Storing backlogs on bookies for a long time can get expensive. If > there are other cheaper forms of storage available (S3/HDFS), capex > can be reduced by moving older data to this storage. > > The proposed design proposes an interface to do this, with an initial > implementation targeted at S3. However the interface is general enough > that HDFS could also be used. > > Design doc: > https://docs.google.com/document/d/1UTMlYA-1XmqIFeyyWPSzva0AmI7vNRsVCEkkde8WYEM/edit?usp=sharing > Prototype/PoC > <https://docs.google.com/document/d/1UTMlYA-1XmqIFeyyWPSzva0AmI7vNRsVCEkkde8WYEM/edit?usp=sharingPrototype/PoC>: > https://github.com/ivankelly/incubator-pulsar/tree/s3-offload-proto > > Cheers, > Ivan > -- Matteo Merli
Re: Presentation on Pulsar "effectively-once"
On Fri, Mar 23, 2018 at 6:23 AM Jim Jagielski wrote: > Agreed. What license are those slides under? > Good question. I haven't really thought of license when uploading the slides. Are there any guidelines/best practicies? Matteo > > > On Mar 10, 2018, at 2:48 PM, Dave Fisher wrote: > > > > Hi Matteo, > > > > Thanks! > > > > Regards, > > Dave > > > >> On Mar 9, 2018, at 9:19 AM, Matteo Merli wrote: > >> > >> These are the slides from the presentation I gave yesterday at Strata > San > >> Jose on "Effectively-once semantics in Apache Pulsar" > >> > >> > https://www.slideshare.net/merlimat/effectivelyonce-semantics-in-apache-pulsar > >> > >> > >> Matteo > >> -- > >> Matteo Merli > >> > > > > -- Matteo Merli
Re: [incubator-pulsar.wiki] branch master updated: Updated Home (markdown)
Hi Dave, Yes, that is the intention for all the PIP proposals :) I just added the proposal to the Wiki for Luc who has not write access to Wiki. He'll be starting the discussion thread on this list soon. Matteo On Thu, Mar 22, 2018 at 10:08 AM Dave Fisher wrote: > Hi - > > The new terminology looks like a good topic for discussion on the dev ML. > > Regards, > Dave > > > > On Mar 22, 2018, at 9:48 AM, mme...@apache.org wrote: > > > > This is an automated email from the ASF dual-hosted git repository. > > > > mmerli pushed a commit to branch master > > in repository > https://gitbox.apache.org/repos/asf/incubator-pulsar.wiki.git > > > > > > The following commit(s) were added to refs/heads/master by this push: > > new 5c91a82 Updated Home (markdown) > > 5c91a82 is described below > > > > commit 5c91a82d9e695ec01f6be92f61267e246440 > > Author: Matteo Merli > > AuthorDate: Thu Mar 22 09:48:00 2018 -0700 > > > >Updated Home (markdown) > > --- > > Home.md | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/Home.md b/Home.md > > index 7ce0db4..b7e152b 100644 > > --- a/Home.md > > +++ b/Home.md > > @@ -5,6 +5,7 @@ > > > > We encourage to document any big change or feature or any addition to > public user APIs through a design document to be discussed with the > community. > > > > +* [PIP 16: Pulsar "instance" terminology change]( > https://github.com/apache/incubator-pulsar/wiki/PIP-16:-Pulsar-%22instance%22-terminology-change > ) > > * [PIP 15: Pulsar Functions]( > https://github.com/apache/incubator-pulsar/wiki/PIP-15:-Pulsar-Functions) > > * [PIP 14: Topic compaction]( > https://github.com/apache/incubator-pulsar/wiki/PIP-14:-Topic-compaction) > > * [PIP 13: Subscribe to topics represented by regular expressions]( > https://github.com/apache/incubator-pulsar/wiki/PIP-13:-Subscribe-to-topics-represented-by-regular-expressions > ) > > > > -- > > To stop receiving notification emails like this one, please contact > > mme...@apache.org. > > -- Matteo Merli
Re: PodlingNameSearch
Sorry for not coming back quickly. Thanks Masakazu for getting this started. Please go ahead and create the ticket. Everyone should be encouraged to chime in and help out with the search. > but prior to creating it, I'd like to make sure that we are going to keep using "Pulsar". Hopefully yes, unless there is a *blocking* reason that prevents us to move forward, we should try to keep same name. Matteo On Fri, Mar 16, 2018 at 10:24 AM Dave Fisher wrote: > Hi Masakazu, > > You are correct. 72 hours have passed. Looking forward to the issue > creation. FYI - I’ve recently joined the Brand committee and will be > reviewing these results. > > Regards, > Dave > > > On Mar 13, 2018, at 8:28 AM, Masakazu Kitajo wrote: > > > > Hi, > > > > Thank you for bringing this up, Dave. > > > > Here's another guide for Podling Name Search. > > https://incubator.apache.org/guides/names.html > > > > According to the guide, a JIRA ticket will be used for records and it > > doesn't seem like one person needs to do all the tasks. Anybody can help > > out by recording facts on the ticket, and we should do this together > since > > we have users and developers in multiple countries. It helps gathering > > facts globally. Then we can ask the trademark team to analyze the facts. > > > > I'm going to create a ticket for Pulsar, but prior to creating it, I'd > like > > to make sure that we are going to keep using "Pulsar". I'll wait for 72 > > hours and create the ticket if no concerns nor proposals ara raised (Lazy > > consensus). > > > > Thanks, > > Masakazu > > > > > > On Wed, Mar 7, 2018 at 11:13 AM, Dave Fisher > wrote: > > > >> Hi Pulsar Team, > >> > >> Would someone submit the Podling Name Search for Pulsar. [1] > >> > >> Regards, > >> Dave > >> > >> [1] https://www.apache.org/foundation/marks/naming.html# > >> create-an-name-search-issue > >> > >> > > -- Matteo Merli
Presentation on Pulsar "effectively-once"
These are the slides from the presentation I gave yesterday at Strata San Jose on "Effectively-once semantics in Apache Pulsar" https://www.slideshare.net/merlimat/effectivelyonce-semantics-in-apache-pulsar Matteo -- Matteo Merli
Re: Pulsar now using standard Apache BookKeeper
On Fri, Mar 2, 2018 at 12:57 PM Dave Fisher wrote: > Hi - > > This is great. Now that this is in the two projects (which share > committers) will need to co-ordinate releases. > > Keep in mind the next Pulsar release needs to be based on a particular > BookKeeper release. An Apache project cannot release against another > project's SNAPSHOT since that has not been validated by their release > process. > Absolutely, we'll switch the the 4.7.0 final release as soon as it's available. The only reason to switch earlier was to have more time to find out potential issues before getting closer to Pulsar release timeline. Matteo -- Matteo Merli
Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3
Hi Stian, thanks for the detailed spot-on review. (comments inline). I have created an issue to track the point you have raised ( https://github.com/apache/incubator-pulsar/issues/1337), we'll get to these before next release. On Fri, Mar 2, 2018 at 2:00 AM Stian Soiland-Reyes wrote: > Oo, I'll better hurry up then! :) > Normally the wording is "The vote is open for at least 72 hours" -- > you are OK to keep it open a bit longer if you need sufficient votes > or have not tallied them yet. > Sure we'll update the email templates > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/ > > pulsar-1.22.0-incubating-candidate-3/ > > Is it fourth of third release candidate? Use consistent numbering. > Starting with "RC0" is a bit unusual.. > Yes, we're indeed starting with RC0. We'll switch the instructions to start with RC1 > +0 src.tar.gz vs git tag (generate_protobuf.sh and > generate_protobuf_docker.sh missing from dist - are they needed?) > These files are only need to recreate protobuf generated files which are anyway included in the repo (not when just c > +0 src NOTICE -- copyright should extend into 2017-2018 > Thanks for catching, will fix > +0 bin NOTICE -- are all of these copyrights really forwarded from their > NOTICE? > > I did a spot check, and guava.jar does not have a NOTICE, so unless > that was copied from a zip/tar that had such a NOTICE, then there > would be nothing to propagate. On the other side netty.jar has a > humongous NOTICE which somehow just becomes "Copyright 2014 The Netty > Project" in your NOTICE -- this seems to violate their Apache license. > Has this been discussed on legael? > This was discussed few times here when voting on past releases. Initially I had put the overall content of Netty NOTICE file but according to the discussion I have only left copyright notices. Discussion for 1.19 Pulsar release: https://lists.apache.org/thread.html/b2ebf0d5fc8f75f3bb09dc1c2da878da9c565043cae8fcc2bb20c519@%3Cgeneral.incubator.apache.org%3E Discussion for 1.20 release: https://lists.apache.org/thread.html/bcaa7b2547ec72d2457c9516ae4fee8bb27429be17a4e0db77b013df@%3Cgeneral.incubator.apache.org%3E These discussions, resulted into these 2 changes to the notice files: * https://github.com/apache/incubator-pulsar/pull/677 * https://github.com/apache/incubator-pulsar/pull/926 Regarding Netty, I've done a spot check on several other ASF TLP projects and found no one including the full NOTICE file from Netty. I can assure we have no intention to withdraw information from the NOTICE file :-), it's just that the definition of what should be included and what shouldn't is still not 100% crisp and clear to us. Your Git repository contains .gitignore.swp from vim which you > probably want to delete. > Thanks for catching, will remove. Your checksum files are in an unusual style: > > C1 B8 C8 91 23 92 6A 56 82 F6 E9 F3 25 86 8B 58 > > CA1B352F 9576C8CB F16258F8 DEABF8F6 E95A926F 665E2FD8 30A38532 8BC639C6 > 20FD34E6 > 6948396A CCD1A123 F072F93D 55D316EB EE34D208 9E0E9174 95AA09EE > > Normally the .md5 and .sha512 files contain the checksum only, in > lowercase hex without spacing, e.g. > > c1b8c89123926a5682f6e9f325868b58 > > ca1b352f9576c8cbf16258f8deabf8f6e95a926f665e2fd830a385328bc639c620fd34e66948396accd1a123f072f93d55d316ebee34d2089e0e917495aa09ee > > This makes it easier to check against tools like md5sum and shasum. > > You didn't include .sha1 checksums, but extra points for .sha512 :) > We have a script that we use to generate the checksums and it does: gpg --print-md SHA512 $FILE > $FILE.sha512 This was to avoid differences in tooling between macos and linux. We'll try to fix it to use the standard format. > It is customary to include the checksums (at least md5) or the > dist.apache.org svn revision in the [VOTE] email, to any avoid > accidental last-minute-tampering confusion and to keep it in the > mailing list archives. > Sure, we'll add that to instructions. Thanks, Matteo -- Matteo Merli
[DRAFT] Podling report March 2018
Drafting here the podling report. Please comment and suggest and I'll be sending the final version before Wednesday. - 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 subscribers, and cross-datacenter replication. Pulsar has been incubating since 2017-06-01. Three most important issues to address in the move towards graduation: 1. Grow the community with new Committers/PPMC members. 2. Complete the Podling name search tasks Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None How has the community developed since the last report? The community added 6 new contributors that submitted pull-requests which were merged into master. There has been a sharp increase in users approaching the team on the Slack channel with many questions on getting started, clarifications, troubleshooting. While developers use Slack for informal chatting, the predominant usage of Slack has be users support. We have created a tool to create daily email digests of the conversation and post it on dev@ and user@ lists, to comply with ASF policy of. We are also extracting the most recurrent questions/answer from Slack and plan to add an FAQ section on the website, together with improving documentation in the areas that seemed more difficult to users. Project members from several companies have organized or participated in several meetups, presenting Pulsar's introductions, deep-dives and hands-on tutorial, including recorded podcasts. We have several scheduled talks on Pulsar at various conferences (such as Strata San Jose on March 8th). How has the project developed since the last report? 22 authors have pushed 536 commits to master in the last 3 months. The project has made the its third and fourth releases since joining the Apache Incubator (1.21.0-incubating on Dec 17th and 1.22.0-incubating on Mar 6th). Project members are actively working on next milestone, 2.0 release that will include several new features including: * Topic compaction * Redesigned type-safe API with schema support * Lightweight compute support Overall, since December, 7 new PIPs (Pulsar Improvement Proposals) for major feature/changes, have been submitted to the wiki and discussed in the mailing list. Since the last report the number of weekly-active-users on the Slack channel has increased from 27 to 53. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [ ] Community building [X] Nearing graduation [ ] Other: Date of last release: 2017-12-13, 1.21.0-incubating 2018-03-06, 1.22.0-incubating When were the last committers or PPMC members elected? 2018-01-19 - Sijie Guo -- Matteo Merli
Re: Podling Report Reminder - March 2018
I'm preparing a draft and I'll send it tomorrow. On Sun, Mar 4, 2018 at 6:45 PM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, March 07). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://wiki.apache.org/incubator/March2018 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC > -- Matteo Merli
Pulsar now using standard Apache BookKeeper
In Pulsar master branch, we have switched the BookKeeper dependency from the Yahoo fork to the 4.7.0-SNAPSHOT version of BookKeeper from main master branch. All the the changes that were in the Yahoo fork, which was based on 4.3.1 release, have been already merged upstream. This was a big effort that took ~ 1 year to get through. There were 246 commits to merge into a codebase that slightly changed in a 4 years timespan. For the curious, this is the spreadsheet we used to track the merging. https://docs.google.com/spreadsheets/d/1jAy3EfjViqNEKpCKpWiRv-PCZGzdjwm_PclL7Obog4Q/ I would like to call out Ivan Kelly & Jia Zhai for giving a big push of porting many of the changes into BookKeeper and the BookKeeper community for being very receptive and helpful in getting this load of changes back into mainline. Matteo -- Matteo Merli
C++/Python features catchup
Since we've been adding a number of new features in Java client library, I have created a project in github to keep track of which features we are missing in the C++ client library (and the Python bindings that are using it). https://github.com/apache/incubator-pulsar/projects/7 Please make sure to create issue (or even just a card in the project) each time a new setting/feature or API is added to the Java client, so that we don't forget to do it in C++. This is also a good list of items for anyone familiar with C++ that has cycles to pick up new tasks ;) Matteo -- Matteo Merli
Fwd: Google Summer of Code 2018 Mentor Registration
Is anyone interested in being a mentor for the summer of code program? Also, does anyone has ideas of good projects that can be proposed? Matteo -- Forwarded message - From: Ulrich Stärk Date: Sat, Feb 24, 2018 at 1:19 PM Subject: Google Summer of Code 2018 Mentor Registration To: Cc: d...@community.apache.org Dear PMCs, I'm happy to announce that the ASF has made it onto the list of accepted organizations for Google Summer of Code 2018! [1,2] It is now time for mentors to sign up, so please pass this email on to your community and podlings. If you aren’t already subscribed to ment...@community.apache.org you should do so now else you might miss important information. Mentor signup requires two steps: mentor signup in Google's system [3] and PMC acknowledgement. If you want to mentor a project in this year's SoC you will have to 1. Be an Apache committer. 2. Request an acknowledgement from the PMC for which you want to mentor projects. Use the below template and *do not forget to copy ment...@community.apache.org*. We will use the email adress you indicate to send the invite to be a mentor for Apache. PMCs, read carefully please. We request that each mentor is acknowledged by a PMC member. This is to ensure the mentor is in good standing with the community. When you receive a request for acknowledgement, please ACK it and cc ment...@community.apache.org Lastly, it is not yet too late to record your ideas in Jira (see my previous emails for details). Students will now begin to explore ideas so if you haven’t already done so, record your ideas immediately! Cheers, Uli mentor request email template: to: private@.apache.org cc: ment...@community.apache.org subject: GSoC 2018 mentor request for PMC, please acknowledge my request to become a mentor for Google Summer of Code 2018 projects for Apache . I would like to receive the mentor invite to [1] https://summerofcode.withgoogle.com/organizations/ [2] https://summerofcode.withgoogle.com/organizations/5718432427802624/ [3] https://summerofcode.withgoogle.com/ -- Matteo Merli
Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3
+1 (binding) Environment: MacOS 10.12 & Centos-7.4 Checked: * Signatures, crc * Bin distribution: - NOTICE, README, LICENSE - Start standalone service and producer/consumer test * Src distribution: - NOTICE, README, LICENSE - Compile and unit tests - Start standalone service * Checked staging maven repository artifacts Matteo On Fri, Feb 23, 2018 at 2:44 AM Jia Zhai wrote: > +1 (non-binding) > > Environment: MacOS 10.13 > > * Bin distribution > -checked md5, sha, asc, > -start standalone, > -producer/consumer worked, > * Src distribution > -checked md5, sha, asc, > -compile and unit tests, > -start standalone, > -producer/consumer worked > > > > > On Fri, Feb 23, 2018 at 4:02 PM, Masahiro Sakamoto > > wrote: > > > +1 (binding) > > > > Environment: CentOS 6.7 > > > > * checked md5, sha, asc > > * ran standalone > > * producer/consumer worked normally > > * compiling and unit tests succeeded > > * rat check > > > > - Masahiro > > > > -- > > Masahiro Sakamoto > > Yahoo Japan Corp. > > E-mail: massa...@yahoo-corp.jp > > -- > > > > > -Original Message- > > > From: Jai Asher [mailto:jai.ashe...@gmail.com] > > > Sent: Wednesday, February 21, 2018 1:39 PM > > > To: dev@pulsar.incubator.apache.org > > > Subject: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3 > > > > > > This is the fourth release candidate for Apache Pulsar, version > > > 1.22.0-incubating. > > > > > > It fixes the following issues: > > > https://github.com/apache/incubator-pulsar/milestone/11?closed=1 > > > > > > *** Please download, test and vote by Friday, Feb 23, 2018, 10:00 GMT. > > > > > > 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/incubator/pulsar/pulsar-1.22.0- > > > incubating-candidate-3/ > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachepulsar-101 > > > 0/ > > > > > > The tag to be voted upon: > > > v1.22.0-incubating-candidate-3 > > > (5d14788e510faec23fd8ed189ed343e93b489dda) > > > https://github.com/apache/incubator-pulsar/releases/tag/v1.22.0-incuba > > > ting-candidate-3 > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > > > > > Please download the source package, and follow the README to build and > > run > > > the Pulsar standalone service. > > > -- Matteo Merli
[BLOG POST] Effectively-once semantics in Apache Pulsar
https://streaml.io/blog/pulsar-effectively-once/ Matteo -- Matteo Merli
Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 1
Jai, I have merged the mentioned fix in master & 1.22 branch. On Mon, Feb 19, 2018 at 9:53 AM Dave Fisher wrote: > Hi - > > Given this comment I’ll wait until tomorrow to review the release. > > Regards, > Dave > > > On Feb 19, 2018, at 9:27 AM, Matteo Merli wrote: > > > > Jai, the artifacts look good. > > > > Though I think we should squeeze in the fix for > > https://github.com/apache/incubator-pulsar/pull/1251 > > That makes partitions unusable on non-persistent topics. > > > > Matteo > > > > On Sat, Feb 17, 2018 at 1:13 AM Jai Asher wrote: > > > >> This is the second release candidate for Apache Pulsar, version > >> 1.22.0-incubating. > >> > >> It fixes the following issues: > >> https://github.com/apache/incubator-pulsar/milestone/11?closed=1 > >> > >> *** Please download, test and vote by Tuesday, Feb 20th, 2018, 10:00 > GMT. > >> > >> 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/incubator/pulsar/pulsar-1.22.0-incubating-candidate-1/ > >> > >> Maven staging repo: > >> > https://repository.apache.org/content/repositories/orgapachepulsar-1008/ > >> > >> The tag to be voted upon: > >> v1.22.0-incubating-candidate-0 > (c7c8a408e377e979350453e06c68340bc66c512c) > >> > >> > https://github.com/apache/incubator-pulsar/releases/tag/v1.22.0-incubating-candidate-1 > >> > >> Pulsar's KEYS file containing PGP keys we use to sign the release: > >> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > >> > >> Please download the source package, and follow the README to build > >> and run the Pulsar standalone service. > >> > > -- > > Matteo Merli > > > > -- Matteo Merli
Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 1
Jai, the artifacts look good. Though I think we should squeeze in the fix for https://github.com/apache/incubator-pulsar/pull/1251 That makes partitions unusable on non-persistent topics. Matteo On Sat, Feb 17, 2018 at 1:13 AM Jai Asher wrote: > This is the second release candidate for Apache Pulsar, version > 1.22.0-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/11?closed=1 > > *** Please download, test and vote by Tuesday, Feb 20th, 2018, 10:00 GMT. > > 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/incubator/pulsar/pulsar-1.22.0-incubating-candidate-1/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1008/ > > The tag to be voted upon: > v1.22.0-incubating-candidate-0 (c7c8a408e377e979350453e06c68340bc66c512c) > > https://github.com/apache/incubator-pulsar/releases/tag/v1.22.0-incubating-candidate-1 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > -- Matteo Merli
Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 0
+1 (binding) Environment: MacOS 10.12 & Centos-7.4 Checked: * Signatures, crc * Bin distribution: - NOTICE, README, LICENSE - Start standalone service and producer/consumer test * Src distribution: - NOTICE, README, LICENSE - Compile and unit tests - Start standalone service * Checked staging maven repository artifacts Matteo On Thu, Feb 15, 2018 at 10:19 PM Jai Asher wrote: > This is the first release candidate for Apache Pulsar, version > 1.22.0-incubating. > > It fixes the following issues: > https://github.com/apache/incubator-pulsar/milestone/11?closed=1 > > *** Please download, test and vote by Tuesday, Feb 20th, 2018, 10:00 GMT. > > 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/incubator/pulsar/pulsar-1.22.0-incubating-candidate-0/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1007/ > > The tag to be voted upon: > v1.22.0-incubating-candidate-0 (96d720c928b21485df8e055dde379aeeb7f81624) > > https://github.com/apache/incubator-pulsar/releases/tag/v1.22.0-incubating-candidate-0 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > -- Matteo Merli
Re: [PROPOSAL] Planning for next releases
Sure, can we also start early in creating the 1.22 branch? We have a lot of changes meant for 2.0 that are waiting to be merged after 1.22. On Thu, Feb 8, 2018 at 9:04 PM Jai Asher wrote: > Hi, > Rajan and I are planning to start the release process on Monday (12 > Feb). > Is everyone fine with this? If yes then kindly get your PR merged by > Monday. > > Regards, > Jai > > On Sun, Jan 21, 2018 at 11:28 PM, Rajan Dhabalia > wrote: > > > Hi, > > > > Yes, we can target 1.22.0-incubating release by reviewing and merging > > pending PRs by end of this month and then we can prepare for 2.0 release. > > > > >> Also, are there any volunteers for release managers for both releases? > > Sure, I can be release manager for 1.22.0-incubating. > > > > Thanks, > > Rajan > > > > > > > > On Fri, Jan 19, 2018 at 3:54 PM, Matteo Merli wrote: > > > > > Since it has already been a while since last release (at least since > when > > > we closed the branch for 1.21), I would like to start discussion and > from > > > my side propose the following: > > > > > > 1. Release 1.22.0-incubating at the end of this month > > > > > >We have already a considerable number of fixes and improvement over > > 1.21 > > > and we should release that, along with pending PRs. I would suggest > > anyone > > > to mark current changes for either this or next release and help with > > > reviewing them. > > > > > > 2. Prepare for 2.0 Pulsar release for end of February. > > > We have been discussing a while back to take the opportunity to > make > > > some changes in API or tools that break binary compatibility, and do > them > > > all at once. > > > I had created a project in Github to track the proposals: > > > https://github.com/apache/incubator-pulsar/projects/4 > > > For this I would also propose to quickly create a branch for 1.22 > so > > > that the work that is targeting 2.0 can be merged into master before > the > > > release is done. > > > > > > Please anyone share your thoughts on this proposal. > > > > > > Also, are there any volunteers for release managers for both releases? > I > > > can also pick up one of them otherwise. > > > > > > Thanks, > > > Matteo > > > > > > > > > > > > -- > > > Matteo Merli > > > > > > > > > -- Matteo Merli
Re: Download page - crypto files links
Dave, I have created https://github.com/apache/incubator-pulsar/pull/1148 with a fix for this. Matteo On Tue, Jan 30, 2018 at 9:59 AM Matteo Merli wrote: > Oh, I see. I think I had misread the last comment on > https://github.com/apache/incubator-pulsar/issues/986 > > So, the download links for the tgzs, should always point to the mirrors, > while KEYS and signatures will all come from dist with HTTPS. > > I'll make the change quickly, thanks for pointing this out. > > Matteo > > On Tue, Jan 30, 2018 at 9:53 AM Dave Fisher wrote: > >> Hi - >> >> I just noticed that the links to the current release asc, md5, and sha512 >> are currently pointing to the mirrors. These need to be adjusted to point >> to the location at dist.apache.org. The reason is that a mirror could be >> compromised or corrupted and these small files used to verify a download >> should be from the master source. >> >> Regards, >> Dave >> > -- > Matteo Merli > > -- Matteo Merli
Re: Download page - crypto files links
Oh, I see. I think I had misread the last comment on https://github.com/apache/incubator-pulsar/issues/986 So, the download links for the tgzs, should always point to the mirrors, while KEYS and signatures will all come from dist with HTTPS. I'll make the change quickly, thanks for pointing this out. Matteo On Tue, Jan 30, 2018 at 9:53 AM Dave Fisher wrote: > Hi - > > I just noticed that the links to the current release asc, md5, and sha512 > are currently pointing to the mirrors. These need to be adjusted to point > to the location at dist.apache.org. The reason is that a mirror could be > compromised or corrupted and these small files used to verify a download > should be from the master source. > > Regards, > Dave > -- Matteo Merli
