Re: [VOTE] Release Apache TubeMQ (Incubating) 0.7.0-incubating RC0

[Sijie Guo]

+1 (binding)

Signatures, checksums, NOTICE, and LICENSE are good.

- Sijie

On Mon, Nov 30, 2020 at 6:27 PM Goson zhang  wrote:

> @Dave Fisher, thank you!
>
> We will continue to improve it.
>
> Dave Fisher  于2020年12月1日周二 上午2:49写道：
>
> > +1 (binding)
> >
> > Signatures, Checksums, DISCLAIMER-WIP, NOTICE, and LICENSE checkout.
> >
> > Rat check looks ok on source. A .rat-excludes file would help as
> licensing
> > is further reviewed.
> >
> > Server binary spot check of license on mvnrepository.com shows proper
> > license choices for selected dependency  jars.
> >
> > Likely the project should be able to attain proper LICENSE in binaries in
> > next release.
> >
> > Best Regards,
> > Dave
> >
> > >This is a call for a vote to release Apache TubeMQ (Incubating)
> > version
> > > 0.7.0-incubating-RC0
> > >
> > >The Apache TubeMQ community has voted on and approved a proposal to
> > > release
> > >Apache TubeMQ (Incubating) version 0.7.0-incubating-RC0
> > >
> > >We now kindly request the Incubator PMC members review and vote on
> > this
> > >incubator release.
> > >
> > >TubeMQ community vote thread:
> > >•
> > >
> >
> https://lists.apache.org/thread.html/r6e3b8e42ad8adb7867780b6aec23cc44b7b55a6a19eecec83aa67b8d%40%3Cdev.tubemq.apache.org%3E
> > >
> > >Vote result thread:
> > >•
> > >
> >
> https://lists.apache.org/thread.html/r459723d31c6f649dcaba6b81ffbccc94cbe53207248966bcc11d7343%40%3Cdev.tubemq.apache.org%3E
> > >
> > >The release candidate:
> > >•
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tubemq/0.7.0-incubating-RC0/
> > >
> > >Git tag for the release:
> > >•
> > https://github.com/apache/incubator-tubemq/tree/0.7.0-incubating-RC0
> > >
> > >Release notes:
> > >•
> > >
> >
> https://github.com/apache/incubator-tubemq/releases/tag/0.7.0-incubating-RC0
> > >
> > >The artifacts signed with PGP key [A4D4D578], corresponding to [
> > > dockerzh...@apache.org], which can be found in the keys file:
> > >• https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
> > >
> > >The vote will be open for at least 72 hours or until the necessary
> > > number of votes are reached.
> > >
> > >Please vote accordingly:
> > >
> > >[ ] +1 approve
> > >[ ] +0 no opinion
> > >[ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > > On behalf of the Apache TubeMQ (Incubating) community.
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

[RESULT] [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

Since 72 hours have passed so the vote is closed with

No -1 votes have been cast.

Thanks,
Sijie


On Fri, Feb 14, 2020 at 12:22 AM Sijie Guo  wrote:

> Hi all,
>
> Apache Pulsar received a donation which adds a pulsar client library
> implemented using .NET.
>
> The IP clearance form can be found at
> https://incubator.apache.org/ip-clearance/pulsar-dotpulsar.html
>
> The contribution can be found at:
> https://github.com/danske-commodities/dotpulsar
> The git repo will be transferred to apache at the end of the process.
>
> Please vote to approve this contribution. Lazy consensus applies: if no -1
> votes are being cast within the next 72 hours, the vote passes.
>
> Thanks,
> Sijie
>

Re: [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

Hi Justin,

Both Daniel and Danske Commodities have signed the SGA. Can you please take
a look at this repo again?

Thanks,
Sijie

On Tue, Feb 18, 2020 at 12:34 PM Sijie Guo  wrote:

> Loop in Daniel from Danske Commodities for clarifications.
>
> I think the project was initially started by Daniel and under his personal
> account. Then after PoC, it was transferred to Danske Commodities GitHub
> organization. I guess when Daniel transferred the repo, they didn't update
> the license copyright. But I think Danske Commodities owns it and is the
> one donating it. Daniel can chime in if I missed something.
>
> Thanks,
> Sijie
>
> On Sun, Feb 16, 2020 at 11:58 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> > Daniel from Danske Commodities has reverted my changes. They have fixed
>> the
>> > license to align with their SGA. Please take a look and let us know if
>> you
>> > have any other questions.
>>
>> Um I’m a little confused it seems the code was originally "Copyright 2018
>> Daniel Blankensteiner” and the IP clearance is from Danske Commodities.
>> From the above I assume Daniel works for Danske Commodities. Which of them
>> actually owns the IPs of the code? Or Is a mixture from both of them? Does
>> Daniel’s employment contract (if one exists) state who owns the IP?
>>
>> Thanks,
>> Justin
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

Loop in Daniel from Danske Commodities for clarifications.

I think the project was initially started by Daniel and under his personal
account. Then after PoC, it was transferred to Danske Commodities GitHub
organization. I guess when Daniel transferred the repo, they didn't update
the license copyright. But I think Danske Commodities owns it and is the
one donating it. Daniel can chime in if I missed something.

Thanks,
Sijie

On Sun, Feb 16, 2020 at 11:58 PM Justin Mclean 
wrote:

> Hi,
>
> > Daniel from Danske Commodities has reverted my changes. They have fixed
> the
> > license to align with their SGA. Please take a look and let us know if
> you
> > have any other questions.
>
> Um I’m a little confused it seems the code was originally "Copyright 2018
> Daniel Blankensteiner” and the IP clearance is from Danske Commodities.
> From the above I assume Daniel works for Danske Commodities. Which of them
> actually owns the IPs of the code? Or Is a mixture from both of them? Does
> Daniel’s employment contract (if one exists) state who owns the IP?
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

Hi Justin,

Daniel from Danske Commodities has reverted my changes. They have fixed the
license to align with their SGA. Please take a look and let us know if you
have any other questions.

Thanks,
Sijie


On Fri, Feb 14, 2020 at 1:16 PM Justin Mclean 
wrote:

> HI,
>
> > Because I see that it was recommended to check and make sure that the
> files
> > that have been donated have been updated to reflect the new ASF
> copyright.
>
> Doing so make to harder to work out the IP provenance of the files or
> check if there’s anything under another license in there.
>
> > I might misunderstand the process here. Do I need to remove "Licensed to
> > the Apache Software Foundation (ASF)”?
>
> No need to remove them.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

Hi Justin,

Daniel from Danske Commodities has incorporated and addressed the comments
here. Please take a look at the repo again and let us know what you think.

Thanks,
Sijie

On Fri, Feb 14, 2020 at 10:21 AM Sijie Guo  wrote:

> + Daniel in the loop.
>
> Thanks,
> Sijie
>
> On Fri, Feb 14, 2020 at 10:20 AM Sijie Guo  wrote:
>
>>
>>
>> On Fri, Feb 14, 2020 at 12:45 AM Justin Mclean 
>> wrote:
>>
>>> Hi,
>>>
>>> I notice the LICENSE fine incorrect states in the appendix "Copyright
>>> 2018 Daniel Blankensteiner” and the files are marked "Licensed to the
>>> Apache Software Foundation (ASF)” this is not correct until after the
>>> donation is accepted.
>>>
>>> Previously the file has no headers, was there any 3rd party code in
>>> there?
>>>
>>
>> Ah, I see. I helped to update the license header in preparing to
>> transfer the repo to the ASF and I used the license header used in Apache
>> Pulsar.
>> https://github.com/danske-commodities/dotpulsar/commit/fb6b6fb898d3d707ab8ceba94a0824e96e5d009d
>>
>>
>> Because I see that it was recommended to check and make sure that the
>> files that have been donated have been updated to reflect the new ASF
>> copyright. I might misunderstand the process here. Do I need to remove
>> "Licensed to the Apache Software Foundation (ASF)"?
>>
>>
>>
>>>
>>> The distribution right are "Danske Commodities A/S” in teh grant but
>>> that doesn’t match with the (incorrect) copyright statement why is this?
>>>
>>
>> I didn't catch "Copyright 2018 Daniel Blankensteiner" in the appendix. I
>> will follow up with the team about this.
>>
>>
>>>
>>> Thanks,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>

Re: [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

+ Daniel in the loop.

Thanks,
Sijie

On Fri, Feb 14, 2020 at 10:20 AM Sijie Guo  wrote:

>
>
> On Fri, Feb 14, 2020 at 12:45 AM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> I notice the LICENSE fine incorrect states in the appendix "Copyright
>> 2018 Daniel Blankensteiner” and the files are marked "Licensed to the
>> Apache Software Foundation (ASF)” this is not correct until after the
>> donation is accepted.
>>
>> Previously the file has no headers, was there any 3rd party code in there?
>>
>
> Ah, I see. I helped to update the license header in preparing to
> transfer the repo to the ASF and I used the license header used in Apache
> Pulsar.
> https://github.com/danske-commodities/dotpulsar/commit/fb6b6fb898d3d707ab8ceba94a0824e96e5d009d
>
>
> Because I see that it was recommended to check and make sure that the
> files that have been donated have been updated to reflect the new ASF
> copyright. I might misunderstand the process here. Do I need to remove
> "Licensed to the Apache Software Foundation (ASF)"?
>
>
>
>>
>> The distribution right are "Danske Commodities A/S” in teh grant but that
>> doesn’t match with the (incorrect) copyright statement why is this?
>>
>
> I didn't catch "Copyright 2018 Daniel Blankensteiner" in the appendix. I
> will follow up with the team about this.
>
>
>>
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

On Fri, Feb 14, 2020 at 12:45 AM Justin Mclean 
wrote:

> Hi,
>
> I notice the LICENSE fine incorrect states in the appendix "Copyright 2018
> Daniel Blankensteiner” and the files are marked "Licensed to the Apache
> Software Foundation (ASF)” this is not correct until after the donation is
> accepted.
>
> Previously the file has no headers, was there any 3rd party code in there?
>

Ah, I see. I helped to update the license header in preparing to
transfer the repo to the ASF and I used the license header used in Apache
Pulsar.
https://github.com/danske-commodities/dotpulsar/commit/fb6b6fb898d3d707ab8ceba94a0824e96e5d009d


Because I see that it was recommended to check and make sure that the files
that have been donated have been updated to reflect the new ASF copyright.
I might misunderstand the process here. Do I need to remove "Licensed to
the Apache Software Foundation (ASF)"?



>
> The distribution right are "Danske Commodities A/S” in teh grant but that
> doesn’t match with the (incorrect) copyright statement why is this?
>

I didn't catch "Copyright 2018 Daniel Blankensteiner" in the appendix. I
will follow up with the team about this.


>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[IP CLEARNCE] Apache Pulsar - DotPulsar

[Sijie Guo]

Hi all,

Apache Pulsar received a donation which adds a pulsar client library
implemented using .NET.

The IP clearance form can be found at
https://incubator.apache.org/ip-clearance/pulsar-dotpulsar.html

The contribution can be found at:
https://github.com/danske-commodities/dotpulsar
The git repo will be transferred to apache at the end of the process.

Please vote to approve this contribution. Lazy consensus applies: if no -1
votes are being cast within the next 72 hours, the vote passes.

Thanks,
Sijie

[RESULT] [IP CLEARANCE] Apache Pulsar - Pulsar Manager

[Sijie Guo]

Since 72 hours have passed so the vote is closed with the following results:

+1:

Matt Sicker

No -1 votes have been cast.

Thanks,
Sijie

On Wed, Sep 11, 2019 at 1:32 PM Sijie Guo  wrote:

> Hi all,
>
> Apache Pulsar received a donation which adds a new web UI - Pulsar Manager
> to Pulsar. Pulsar Manager is a web-based GUI management and monitoring
> tool that helps
> administrators and users manage and monitor tenants, namespaces, topics,
> subscriptions, brokers, clusters, and so on, and supports dynamic
> configuration of multiple environments.
>
> The IP clearance form can be found at:
> http://incubator.apache.org/ip-clearance/pulsar-manager.html
>
> The contribution can be found at:
> https://github.com/streamnative/pulsar-manager
> The git repo will be transferred to apache at the end of the process.
>
> Please vote to approve this contribution. Lazy consensus applies: if no -1
> votes are being cast within the next 72 hours, the vote passes.
>
> Thanks,
> Sijie
>
>
>

[IP CLEARANCE] Apache Pulsar - Pulsar Manager

[Sijie Guo]

Hi all,

Apache Pulsar received a donation which adds a new web UI - Pulsar Manager
to Pulsar. Pulsar Manager is a web-based GUI management and monitoring tool
that helps
administrators and users manage and monitor tenants, namespaces, topics,
subscriptions, brokers, clusters, and so on, and supports dynamic
configuration of multiple environments.

The IP clearance form can be found at:
http://incubator.apache.org/ip-clearance/pulsar-manager.html

The contribution can be found at:
https://github.com/streamnative/pulsar-manager
The git repo will be transferred to apache at the end of the process.

Please vote to approve this contribution. Lazy consensus applies: if no -1
votes are being cast within the next 72 hours, the vote passes.

Thanks,
Sijie

Re: Incubator Clutch Analysis Job failed

[Sijie Guo]

Thank you Dave.

+ dev@tamaya

After looking at the issue a bit more, it seems some how the `www` field in
tamaya's status page confused the clutch2 script.

```
  
Original: https://github.com/java-config;>
https://github.com/java-config
Podling: http://tamaya.incubator.apache.org/;>
http://tamaya.incubator.apache.org/
  
```

The clutch2.py script interprets the url as `tamaya: urlWww=
https://github.com/java-config  http://tamaya.incubator.apache.org/`.
Hence the script attempts to create an url with path "/java-config
http://tamaya.incubator.apache.org/; and python throws InvalidUrlException.

I grep the output. It seems that tamaya is the only one project has this
problem. I am wondering can we do a quick fix on the tamaya status page to
bring the build back first.

Thoughts?

```
amaterasu: urlWww=http://amaterasu.incubator.apache.org/
annotator: urlWww=http://annotator.incubator.apache.org/
batchee: urlWww=http://batchee.incubator.apache.org
brpc: urlWww=http://brpc.incubator.apache.org/
crail: urlWww=http://crail.incubator.apache.org/
daffodil: urlWww=http://daffodil.incubator.apache.org/
datasketches: urlWww=http://datasketches.apache.org/
dlab: urlWww=http://dlab.incubator.apache.org/
dolphinscheduler: urlWww=http://dolphinscheduler.incubator.apache.org/
doris: urlWww=http://doris.incubator.apache.org/
druid: urlWww=https://druid.apache.org/
edgent: urlWww=http://edgent.incubator.apache.org/
flagon: urlWww=http://flagon.incubator.apache.org
gobblin: urlWww=http://incubator.apache.org/gobblin/
heron: urlWww=http://heron.incubator.apache.org/
hivemall: urlWww=http://hivemall.incubator.apache.org/
hudi: urlWww=http://hudi.incubator.apache.org/
iceberg: urlWww=http://iceberg.incubator.apache.org/
iotdb: urlWww=http://iotdb.incubator.apache.org/
livy: urlWww=https://livy.incubator.apache.org/
marvin-ai: urlWww=http://marvin.incubator.apache.org/
milagro: urlWww=http://milagro.incubator.apache.org/
mxnet: urlWww=http://mxnet.incubator.apache.org/
myriad: urlWww=http://myriad.incubator.apache.org
nemo: urlWww=http://nemo.incubator.apache.org/
omid: urlWww=http://omid.incubator.apache.org/
pagespeed: urlWww=http://pagespeed.incubator.apache.org/
pinot: urlWww=http://pinot.incubator.apache.org/
ponymail: urlWww=http://ponymail.incubator.apache.org/
ratis: urlWww=http://ratis.incubator.apache.org/
rya: urlWww=http://rya.incubator.apache.org/
s2graph: urlWww=http://s2graph.incubator.apache.org/
samoa: urlWww=http://samoa.incubator.apache.org/
sdap: urlWww=http://sdap.incubator.apache.org
shardingsphere: urlWww=https://shardingsphere.incubator.apache.org/
singa: urlWww=http://singa.incubator.apache.org/
spot: urlWww=http://spot.incubator.apache.org/
superset: urlWww=http://superset.incubator.apache.org/
tamaya: urlWww=https://github.com/java-config
http://tamaya.incubator.apache.org/
taverna: urlWww=https://taverna.incubator.apache.org/
tephra: urlWww=http://tephra.incubator.apache.org/
toree: urlWww=https://toree.apache.org
training: urlWww=http://training.incubator.apache.org/
tuweni: urlWww=http://tuweni.apache.org/
tvm: urlWww=http://tvm.incubator.apache.org/
weex: urlWww=http://weex.incubator.apache.org/
```

- Sijie

On Tue, Sep 10, 2019 at 4:13 PM Dave Fisher  wrote:

> Hi -
>
> Thanks for fixing the problem with Rya’s status page.
>
> I’m not sure what is happening with this error. It works on python 3.7.3
> but not on the build bot.
>
> If at ACNA and will talk directly with Infra and/or figure out whatever
> the error is.
>
> Thanks,
> Dave
>
> > On Sep 10, 2019, at 3:29 PM, Sijie Guo  wrote:
> >
> > Hi all,
> >
> > I added an ip-clearance form to incubator website a few days ago. But it
> > didn't show up in the website. Hence I took a look at the incubator
> website
> > build jobs. It seems the "Incubator Clutch Analysis Job" keeps failing
> > since 09/01 (
> >
> https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
> > ).
> >
> > I checkout the incubator and run `./build_local_clutch.sh` locally. It
> > seems to work. But the Jenkins job fails with following errors. Anyone
> > knows what can be the problem?
> >
> > ```
> >
> > Traceback (most recent call last):
> >  File "clutch2.py", line 1051, in 
> >getUrl(url)
> >  File "clutch2.py", line 220, in getUrl
> >resp = urllib.request.urlopen(url, timeout=5)
> >  File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen
> >return opener.open(url, data, timeout)
> >  File "/usr/lib/python3.6/urllib/request.py", line 526, in open
> >response = self._open(req, data)
> >  File "/usr/lib/python3.6/urllib/request.py", line 544, in _open
> >'_open', re

Incubator Clutch Analysis Job failed

[Sijie Guo]

Hi all,

I added an ip-clearance form to incubator website a few days ago. But it
didn't show up in the website. Hence I took a look at the incubator website
build jobs. It seems the "Incubator Clutch Analysis Job" keeps failing
since 09/01 (
https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/
).

I checkout the incubator and run `./build_local_clutch.sh` locally. It
seems to work. But the Jenkins job fails with following errors. Anyone
knows what can be the problem?

```

Traceback (most recent call last):
  File "clutch2.py", line 1051, in 
getUrl(url)
  File "clutch2.py", line 220, in getUrl
resp = urllib.request.urlopen(url, timeout=5)
  File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.6/urllib/request.py", line 526, in open
response = self._open(req, data)
  File "/usr/lib/python3.6/urllib/request.py", line 544, in _open
'_open', req)
  File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
result = func(*args)
  File "/usr/lib/python3.6/urllib/request.py", line 1361, in https_open
context=self._context, check_hostname=self._check_hostname)
  File "/usr/lib/python3.6/urllib/request.py", line 1318, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
  File "/usr/lib/python3.6/http/client.py", line 1254, in request
self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.6/http/client.py", line 1265, in _send_request
self.putrequest(method, url, **skips)
  File "/usr/lib/python3.6/http/client.py", line 1127, in putrequest
raise InvalidURL(f"URL can't contain control characters. {url!r} "
http.client.InvalidURL: URL can't contain control characters.
'/java-config  http://tamaya.incubator.apache.org' (found at least '
')

```

Thanks,
Sijie

Re: [VOTE] Shut down unused/inactive incubator lists

[Sijie Guo]

+1

On Sun, Jan 20, 2019 at 4:12 PM sebb  wrote:

> The following lists are all but inactive:
>
> announce@ Last post Jan 2008
> android-interest@ Last post Mar 2011
> dev@ - only general circulars
> jaxws-tck@ (private) Last post 2012
> projects@ Last post Jul 2011
> user@ - only general circulars
>
> I think they should be shut down.
>
> Please vote so an Infra Jira can be raised to shut them down.
> They can have a bounce message added to direct posters to
> general@/private@ as appropriate
>
> [  ] +1
> [  ] -1 - give a reason please
>
> Please vote by end January 2019
>
> Sebb.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

[Sijie Guo]

+1!! (non-binding)

- Sijie

On Wed, Sep 12, 2018 at 8:40 AM Dave Fisher  wrote:

> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> 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.
>

Re: [DISCUSS] Graduate Apache Pulsar (incubating) as a TLP

[Sijie Guo]

Justin,


On Mon, Sep 10, 2018 at 9:34 PM Justin Mclean  wrote:

> Hi,
>
> Just a couple of minor things I noticed on the website which checking it.
> While this is mostly red [1] all seems all links are there other than
> Events?


I think the red links are related to the podling checker code. I think the
checker code checks the plain html files.
Pulsar website was built using https://docusaurus.io/, which is based on
react. The Apache dropdown menu is rendered by javascript.
I am not sure how to fix it to compromise the checker.

will try to include the Apache event in the website.



> 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?


> and why Matteo is listed as the co-creator here [3]. Nothing that would
> stop graduation of course.
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/pods/project/pulsar
> 2. http://pulsar.apache.org/en/team/
> 3. http://pulsar.apache.org/en/resources/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache Pulsar (incubating) as a TLP

[Sijie Guo]

sebb,

Thank you for pointing them out.
I will fix the download links.

- Sijie

On Tue, Sep 11, 2018 at 4:42 AM sebb  wrote:

> Just noticed that the download page links to
>
> https://archive.apache.org/dist/incubator/pulsar/
>
> for current sigs and hashes.
> It should use the following for current releases:
>
> https://www.apache.org/dist/incubator/pulsar/
>
> The host archive.apache.org is only for archived releases.
>
> [Also the page includes SHA1 links; these have since been deprecated
> and could just be dropped]
>
> The link to the KEYS file is correct.
>
>
>
> On 11 September 2018 at 12:32, Justin Mclean  wrote:
> > Hi,
> >
> >> Even Events is there under the Community tab.
> >
> > That seems to be project events rather than Apache events - but again
> it’s a very minor thing.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[ANNOUNCE] Apache Pulsar 2.1.0-incubating released

[Sijie Guo]

The Apache Pulsar team is proud to announce Apache Pulsar version
2.1.0-incubating.

This is the seventh Pulsar release after entering the Apache Incubator.

Pulsar is a highly scalable, low latency messaging streaming platform
running on
commodity hardware. It provides simple pub/sub semantics over topics,
supports
at-least-once and effectively-once delivery of messages, automatic cursor
management
for subscribers, and multi-tenancy and cross-datacenter replication.
Additionally,
it also provides lightweight stream native processing through Pulsar
Functions.

2.1.0-incubating release introduces several major features and improvements
from many contributors. These major features include:

- Pulsar IO : A
serverless inspired connector framework for moving data in and out of
Apache Pulsar leveraging Pulsar Functions
. 6
builtin connectors are included: Kafka
, Kinesis
, RabbitMQ
, Aerospike
, Cassandra
 and Twitter
Firehose .

- Tiered Storage
: An
offloading mechanism in Pulsar segment store to offload old segments from
Apache BookKeeper into long term storage such as HDFS, S3, GCS. S3 is
currently supported in this release.

- Stateful Function
: Pulsar
Functions introduces a new State API
 to store
function state back to Apache BookKeeper. It is a deep integration with
BookKeeper's table service and it will simplify developing stateful
applications using Pulsar Functions. It is available as a developer-preview
feature in Java SDK.

- Go Client
: A cgo
wrapper over existing c++ client.

- More Schemas are introduced, including Avro

and Protobuf

.


For Pulsar release details and downloads, visit:

https://pulsar.incubator.apache.org/download

Release Notes are at:
http://pulsar.apache.org/release-notes/#2.1.0-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.

[Result] [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

The vote is now closed with 3 +1s and no -1s.

Binding +1s

 * Dave Fisher
 * Justin Mclean
 * Jim Jagielski


Thank you,
Sijie

On Wed, Jul 25, 2018 at 11:17 AM Sijie Guo  wrote:

> This is the 5th release candidate for Apache Pulsar, version
> 2.1.0-incubating.
>
> Link to the vote on dev@pulsar list:
> https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware.
> It provides simple pub-sub semantics over topics, guaranteed at-least-once
> and effective-once delivery of messages, automatic cursor management for
> subscribers, and geo-replication.
>
> This is a feature release, introducing following new features:
>
> - Pulsar I/O: a serverless connector framework built on top of Pulsar
> 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 voting 2.1.0 release:
>
> - For compiling source distribution, use "mvn clean install  
> -Dmaven.gitcommitid.skip=true
> [-DskipTests]".
> - Starting from this release, Pulsar is shipping RPM & DEB packages for
> pulsar non-java clients.
> - Starting from this release, Pulsar is shipping a binary distribution
> called `apache-pulsar-io-connectors`
>   including all built-in connectors. Each connector is packaged with all
> their dependencies and
>   a META-INF/DEPEDENCIES file with licensing information for
> all dependencies.
> - Since there are a lot of features introduced in 2.1, You can use the
> instructions documented in the link for
>   validating the binary release candidate:
> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation
>
> - Sijie
>
>

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

On Tue, Jul 31, 2018 at 5:43 AM Justin Mclean 
wrote:

> HI,
>
> I would be +1 (binding) but can’t compile from source so sorry but it’s -1
> (binding) form me. This could be an error on my part and if so I’ll be
> happy to change my vote.
>
> I checked fo rtes source release:
> - incubating in name
> - hashes and signatures good
> - DISCLAIMER exits
> - LICENSE and NOTICE all good
> - all source files have ASF headers
> - no unexpected binaries
> - can’t compile source release as it looks like it assumes it’s been
> checked out from git
>
> Error when compiling:
> [ERROR] Failed to execute goal
> pl.project13.maven:git-commit-id-plugin:2.2.4:revision (git-info) on
> project protobuf-shaded: .git directory is not found! Please specify a
> valid [dotGitDirectory] in your pom.xml -> [Help 1]
>
> Possible the compile instruction in README may be missing a step or am i
> doing something wrong?
>
> Also the binary NOTICE needs a little work and incorrectly lists bundled
> projects copyrights, only relocated copyright statements or those mentioned
> in NOTICE files need to be included in NOTICE. It also has the incorrect
> year. Be great if you could fix this up for the next release.
>

I create an issue for tracking this -
https://github.com/apache/incubator-pulsar/issues/2271

We will address in the upcoming 2.1.1 release.


>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

Thank you Justin.
On Tue, Jul 31, 2018 at 7:46 AM Justin Mclean 
wrote:

> Hi,
>
> Changing to +1 (binding) but please raise a JIRA and fix for next release.
>
> > I had the same experience and response. See this email for the solution.
> >
> >
> https://lists.apache.org/thread.html/0744146fe14b23753d3a7c9c08885a74a76b30a1885cb12bd49381c5@%3Cdev.pulsar.apache.org%3E
>
> I tried  the -Dmaven.gitcommitid.skip=true option and was getting:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile
> (default-compile) on project pulsar-common: Compilation failure:
> Compilation failure:
> [ERROR]
> /Users/justinmclean/ApachePulsar/apache-pulsar-2.1.0-incubating/pulsar-common/src/main/java/org/apache/pulsar/common/api/proto/PulsarApi.java:[6727,56]
> package org.apache.pulsar.shaded.com.google.protobuf.v241 does not exist
> seem you must
>
> But it seems you need to install rather than just compile, so looks like
> something is a little broken here. Also the instructions in README.md say
> only "mvn install -DskipTests" so they also need to be updated.
>

I had a Github issue tracking on addressing the git-commit-id plugin, which
will be addressed in 2.1.1 release.


>
> Thanks,
> Justin
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

Can any people from IPMC help review and vote this release?

Sijie

On Wed, Jul 25, 2018 at 11:17 AM Sijie Guo  wrote:

> This is the 5th release candidate for Apache Pulsar, version
> 2.1.0-incubating.
>
> Link to the vote on dev@pulsar list:
> https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware.
> It provides simple pub-sub semantics over topics, guaranteed at-least-once
> and effective-once delivery of messages, automatic cursor management for
> subscribers, and geo-replication.
>
> This is a feature release, introducing following new features:
>
> - Pulsar I/O: a serverless connector framework built on top of Pulsar
> 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 voting 2.1.0 release:
>
> - For compiling source distribution, use "mvn clean install  
> -Dmaven.gitcommitid.skip=true
> [-DskipTests]".
> - Starting from this release, Pulsar is shipping RPM & DEB packages for
> pulsar non-java clients.
> - Starting from this release, Pulsar is shipping a binary distribution
> called `apache-pulsar-io-connectors`
>   including all built-in connectors. Each connector is packaged with all
> their dependencies and
>   a META-INF/DEPEDENCIES file with licensing information for
> all dependencies.
> - Since there are a lot of features introduced in 2.1, You can use the
> instructions documented in the link for
>   validating the binary release candidate:
> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation
>
> - Sijie
>

Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

Thank you Willem!

On Sun, Jul 29, 2018 at 5:45 PM Willem Jiang  wrote:

> Hi Sijie
>
> I just have a quick question for the apache-pulsar-io-connectors-
> 2.1.0-incubating-bin.tar.gz.
> I guess the source is from apache-pulsar-2.1.0-incubating-src.tar.gz, but I
> need to know how to build this artifact.
>

Ah, when you run "mvn clean install -Dmaven.gitcommitid.skip=true
-DskipTests", the apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz
will be produced under `distribution/io/target` directory. This is the io
binary bundle contains all the built-in connectors.

>
> BTW, it looks like the License of
> apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz
> doesn't reflect the bundled third party dependencies.
>

We are using NIFI NAR plugin for packing io connector. for each connector,
a META-INF/DEPENDENCIES file with licensing  information for all its
transitive dependencies is bundled with each NAR package.


>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Jul 26, 2018 at 2:17 AM, Sijie Guo  wrote:
>
> > This is the 5th release candidate for Apache Pulsar, version
> > 2.1.0-incubating.
> >
> > Link to the vote on dev@pulsar list:
> > https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416
> > b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E
> >
> > Pulsar is a highly scalable, low latency messaging platform running on
> > commodity hardware.
> > It provides simple pub-sub semantics over topics, guaranteed
> at-least-once
> > and effective-once delivery of messages, automatic cursor management for
> > subscribers, and geo-replication.
> >
> > This is a feature release, introducing following new features:
> >
> > - Pulsar I/O: a serverless connector framework built on top of Pulsar
> > 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 voting 2.1.0 release:
> >
> > - For compiling source distribution, use "mvn clean install
> > -Dmaven.gitcommitid.skip=true
> > [-DskipTests]".
> > - Starting from this release, Pulsar is shipping RPM & DEB packages for
> > pulsar non-java clients.
> > - Starting from this release, Pulsar is shipping a binary distribution
> > called `apache-pulsar-io-connectors`
> >   including all built-in connectors. Each connector is packaged with all
> > their dependencies and
> >   a META-INF/DEPEDENCIES file with licensing information for
> > all dependencies.
> > - Since there are a lot of features introduced in 2.1, You can use the
> > instructions documented in the link for
> >   validating the binary release candidate:
> > https://github.com/apache/incubator-pulsar/wiki/Release-
> > Candidate-Validation
> >
> > - Sijie
> >
>

[VOTE] Pulsar Release 2.1.0-incubating Candidate 5

[Sijie Guo]

This is the 5th release candidate for Apache Pulsar, version
2.1.0-incubating.

Link to the vote on dev@pulsar list:
https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E

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

This is a feature release, introducing following new features:

- Pulsar I/O: a serverless connector framework built on top of Pulsar
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 voting 2.1.0 release:

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

- Sijie

Re: [VOTE] Accept Doris into the Apache Incubator

[Sijie Guo]

umentation ==
>
> Information about Doris can be found at https://github.com/baidu/palo.
> The following links provide more information about Doris in open source:
>
>  * Doris wiki site: https://github.com/baidu/palo/wiki
>  * Codebase at Github: https://github.com/baidu/palo
>  * Issue Tracking: https://github.com/baidu/palo/issues
>  * Overview: https://github.com/baidu/Doris/wiki/palo-Overview
>  * FAQ: https://github.com/baidu/palo/wiki/palo-FAQ
>
> == Initial Source ==
>
> Doris has been under development since 2017 by a team of engineers at
> Baidu Inc. It is currently hosted on Github.com under an Apache license
> at https://github.com/baidu/palo.
>
> == External Dependencies ==
>
> Doris has the following external dependencies.
>
>  * Google gflags (BSD)
>  * Google glog (BSD)
>  * Apache Thrift (Apache Software License v2.0)
>  * Apache Commons (Apache Software License v2.0)
>  * Boost (Boost Software License)
>  * rapidjson (Tencent)
>  * Google RE2 (BSD-style)
>  * lz4 (BSD)
>  * snappy (BSD)
>  * Twitter Bootstrap (Apache Software License v2.0)
>  * d3 (BSD)
>  * LLVM (BSD-like)
>
> Build and test dependencies:
>
>  * Apache Ant (Apache Software License v2.0)
>  * Apache Maven (Apache Software License v2.0)
>  * cmake (BSD)
>  * clang (BSD)
>  * Google gtest (Apache Software License v2.0)
>
> == Required Resources ==
>
> === Mailing List ===
>
> There are currently no mailing lists. The usual mailing lists are expected
> to be set up when entering incubation:
>
>  * priv...@doris.incubator.apache.org
>  * d...@doris.incubator.apache.org
>  * comm...@doris.incubator.apache.org
>
> === Subversion Directory ===
>
> Upon entering incubation, we want to move (or copy) the existing repo from
> https://github.com/baidu/palo to Apache infrastructure at
> https://github.com/apache/incubator-doris.
>
> === Issue Tracking ===
>
> Doris currently uses GitHub to track issues. Would like to continue to do
> so while we discuss migration possibilities with the ASF Infra committee.
>
> === Other Resources ===
>
> The existing code already has unit tests so we will make use of existing
> Apache continuous testing infrastructure. The resulting load should not be
> very large.
>
> == Initial Committers ==
>
>  * Ruyue Ma (https://github.com/maruyue, maruyue@baidu dot com)
>  * Chun Zhao (https://github.com/imay, buaa.zhaoc@gmail dot com)
>  * Mingyu Chen (https://github.com/morningman,chenmingyu@baidu dot com)
>  * De Li（https://github.com/lide-reed, mailtolide@sina dot com）
>  * Hao Chen (https://github.com/chenhao7253886, chenhao16@baidu dot com)
>  * Chaoyong Li (https://github.com/cyongli, lichaoyong@baidu dot com)
>  * Bin Lin (https://github.com/lingbin, lingbinlb@gmail dot com)
>  * Sijie Guo (guosijie@gmail dot com)
>  * Zheng Shao (zs...@apache.org)
>
> == Affiliations ==
>
> The initial committers are employees of Baidu Inc..
>
> == Sponsors ==
>
> === Champion ===
>
>  * Dave Fisher, w...@apache.org
>
> === Nominated Mentors ===
>
>  * Luke Han, luke...@apache.org
>  * Dave Fisher, w...@apache.org
>  * Willem Jiang, ningji...@apache.org
>
> === Sponsoring Entity ===
>
> We are requesting the Incubator to sponsor this project.
>
>

Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2

[Sijie Guo]

Can anyone in IPMC help reviewing this? Since there are some user facing
issues reported at mailing lists and slack channel regarding 2.0.0 release,
we would like to get 2.0.1 release out as soon as this release passed
reviews.

Thank you,
Sijie

On Thu, Jun 14, 2018 at 2:22 PM Matteo Merli  wrote:

> Hi WIllem,
>
> the 2.0.1 candidate was already being voted on the dev@pulsar list when
> the
> comments on 1.22.1 release were made here on incubator list, otherwise we
> would have included the changes.
>
> 2.0.1 is a patch release in which we are trying to fix some issues reported
> by
> users in the 2.0.01-rc1 release from a couple of weeks back.
>
> Since at least a couple of issues were impacting users, we were trying to
> get
> a fix out ASAP. In particular we found packaging related issues that
> impacted:
>  * Pulsar python client lib
>  * Pulsar proxy startup
>
> Master branch is already set on 2.1 release and we just applied few commits
> to fix the non-functioning features.
>
> The idea was to fix netty packaging and protobuf license headers for 2.1,
> for
> which we plan to start the release process by next week.
>
> Matteo
>
> On Wed, Jun 13, 2018 at 6:24 PM Willem Jiang 
> wrote:
>
> > Hi Matto,
> >
> > I just checked the source code, the License header issue is still there.
> > pulsar-common/src/main/java/org/apache/pulsar/common/util/
> > protobuf/ByteBufCoded{Input,Output}Stream.java
> >
> > There are still bunch different version of netty jars in the lib
> directory.
> >
> > My suggestion is we need fix these issues that we found in the last vote
> > before starting a new vote.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jun 12, 2018 at 6:00 AM, Matteo Merli  wrote:
> >
> > > This is the second release candidate for Apache Pulsar, version
> > > 2.0.1-incubating.
> > >
> > > Link to the vote on dev@pulsar list
> > > https://lists.apache.org/thread.html/620813d66d43a43680d3afd587e72f
> > > 0d6f9607f1566aa88ef73d359c@%3Cdev.pulsar.apache.org%3E
> > >
> > > 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.
> > >
> > > 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
> > >  > > 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
> > > 
> > >
> >
> --
> Matteo Merli
> 
>

Re: [VOTE] Pulsar Release 1.22.1-incubating Candidate 2

[Sijie Guo]

+1 (repeated my +1 from dev@ votes)

On Thu, Jun 7, 2018 at 11: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-2 (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.
>

Re: Deploying Omid release 0.9.0.0

[Sijie Guo]

It seems to publish the maven artifacts to bintray.com, not apache
repository.

just took a quick look at your pom.xml, it seems that your profile doesn't
inherit from Apache POM, which will help you setup the distribution
management section to use the correct release / snapshot repositories.

You can checkout the instructions here -
http://www.apache.org/dev/publishing-maven-artifacts.html

Hope this helps!

- Sijie

On Wed, Jun 6, 2018 at 1:20 AM Ohad Shacham  wrote:

> Hi All,
>
> I am trying to deploy Omid 0.9.0.0 release and get the following error:
>
> [*ERROR*] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy *(default-deploy)*
> on project omid: *Failed to deploy artifacts: Could not transfer artifact
> org.apache.omid:omid:pom:0.9.0.0 from/to bintray
> (https://api.bintray.com/maven/yahoo/maven/omid
> ): Failed to transfer
> file:
>
> https://api.bintray.com/maven/yahoo/maven/omid/org/apache/omid/omid/0.9.0.0/omid-0.9.0.0.pom
> <
> https://api.bintray.com/maven/yahoo/maven/omid/org/apache/omid/omid/0.9.0.0/omid-0.9.0.0.pom
> >.
> Return code is: 401, ReasonPhrase: Unauthorized.* -> *[Help 1]*
>
> I am using command:
> mvn deploy -Phbase-1 -Prelease_profile -DskipTests
>
> The release tag is:
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?
> p=incubator-omid.git;a=tag;h=229831bc377e47431cc7cbc211803069158b5711
>
> and the repository is:
>
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git
>
> Can anyone please advise?
>
> Thanks,
> Ohad
>

Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!

[Sijie Guo]

Congratulations Justin!

- Sijie

On Mon, Jun 4, 2018 at 3:12 AM, Bertrand Delacretaz 
wrote:

> Hi,
>
> John D. Ament recently announced his desire to step down from the
> Incubator PMC chair role. Thank you so much John for your efficient
> service here, "retiring" from that is certainly well deserved!
>
> The Incubator PMC had the difficult task of choosing between a handful
> of excellent candidates and has selected Justin as our new chair. The
> ASF's Board of Directors has ratified this choice at our May meeting.
>
> Please join me in welcoming Jusin as our new PMC chair! Justin's been
> very active in the Incubator in the last few years, it's great to see
> him step up to this role.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 5

[Sijie Guo]

Thank you Willem. Comments inline

On Fri, May 25, 2018 at 4:03 PM, Willem Jiang 
wrote:

> my +1.
>
> I checked:
>
> The sign and check sum for both src and binary distributions.
> The License and Notice file for src and binary distributions.
> I can build the binary from source.
>
> Here are some minor issues I found, it's not blocker issues please verify
> them and we can fix it in the next release.
>
> 1. It's a little big size for the binary ,  so I checked the files.
> It looks like there are java-instance.jar which holds all the jars in the
> lib directory. I think we need to find a way to avoid shipping the jars
> twice.
>

java-instance.jar is a uber jar including all the dependencies for running
pulsar functions in process mode.

it is needed for this release, because there are conflicts between
different protobuf/netty versions. so we have to do proper shading to
handle that.

we are addressing that in master, the situation can be improved in 2.1
release.


>
> 2. There are three different version of Netty in the library,
> io.netty-netty-3.10.1.Final.jar
> io.netty-netty-all-4.1.21.Final.jar
> io.netty-netty-codec-http2-4.1.12.Final.jar
>
> as netty 3.x and netty4.x use different package name, we may need to go
> through all the netty 4.x dependencies.
>

yeah. pulsar is using 4.1.21, however 3.10.1 and 4.1.12 are coming from its
transitive dependencies. hope that clarifies.


>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, May 24, 2018 at 1:21 PM, Matteo Merli  wrote:
>
> > This is the fifth 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.
> >
> > The only difference from previous candidate is a fix on the LICENSE
> > attached to bin distribution to correctly reflect all dependencies and
> > versions.
> >
> > Link to the voting thread on pulsar dev list:
> > https://lists.apache.org/thread.html/81359fe55cb75cd1621a70e9a5a0af
> > 02fb1a84549ab0046d335182fa@%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-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
> > 
> >
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

On Mon, May 14, 2018 at 11:16 AM, Dave Fisher <dave2w...@comcast.net> wrote:

> Hi -
>
> > On May 14, 2018, at 10:57 AM, Sijie Guo <guosi...@gmail.com> wrote:
> >
> > On Sun, May 13, 2018 at 7:49 PM, Matt Sicker <boa...@gmail.com> wrote:
> >
> >> On 13 May 2018 at 12:10, Matteo Merli <mme...@apache.org> wrote:
> >>
> >>> 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.
> >>>
> >>
> >> By generating the binary jar from source files at test time, you'd avoid
> >> bundling any binary output files.
> >>
> >
> > I made the original change long time back in pulsar-functions for testing
> > submitting user-defined function. When we first contribute
> pulsar-functions
> > to pulsar, we probably didn't clean that up.
> > The intention behind that change is not including any source code or jar
> in
> > the test dependency tree. As including source code would make the testing
> > function as part of the test dependency, it would volatile the purpose of
> > testing submitting a user defined function. In this case,
> > "multifunction.jar" is the a "user-defined" function as the test
> resource.
>
> To be succinct The ASF produces open source software and including a
> pre-compiled binary in the release means that the project fails the open
> source definition. [1]
>
> It really doesn’t matter how or why. You will need to provide the source
> (as simple as it might be) and the maven configuration to build that
> trivial jar.
>

Okay. So if we provide the source file of that jar, is it allowed to
include a pre-compiled binary as test resources?



>
> Regards,
> Dave
>
> [1] https://opensource.org/osd
>
> >
> >
> >
> >
> >
> >>
> >>
> >>>> (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.
> >>>
> >>
> >> Sorry for the confusion, that was just an example from a problem I've
> seen
> >> before in another project.
> >>
> >> --
> >> Matt Sicker <boa...@gmail.com>
> >>
>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

On Mon, May 14, 2018 at 10:53 AM, Matt Sicker <boa...@gmail.com> wrote:

> I'm not sure about a specific policy, but sources by definition aren't the
> binaries. Sources combine with a tool or tools to create binaries.
>

Okay. But this is a test "resource" used by other sources on testing.

Image you are writing an image processing library, you include some
"images" for testing the library. Is it allowed to include those "images"
in the source release?

If you change "image" to "functions", pulsar-functions provides a
framework/library for processing functions, we include some user-defined
"functions" (aka jars) as test resources for testing the library. Is it
allowed or not?

>From what I can see here, the jars included in source binary are test
resources for testing. What is the ASF policy for handling test resources?


- Sijie




>
> On 14 May 2018 at 12:41, Sijie Guo <guosi...@gmail.com> wrote:
>
> > On Sat, May 12, 2018 at 3:52 PM, Justin Mclean <jus...@classsoftware.com
> >
> > wrote:
> >
> > > Hi,
> > >
> > > Sorry but it’s -1 binding due to compiled code in source release.
> > >
> >
> >
> > Can anyone point me the ASF policy page about this - "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 <boa...@gmail.com>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

On Sun, May 13, 2018 at 7:49 PM, Matt Sicker  wrote:

> On 13 May 2018 at 12:10, Matteo Merli  wrote:
>
> > 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.
> >
>
> By generating the binary jar from source files at test time, you'd avoid
> bundling any binary output files.
>

I made the original change long time back in pulsar-functions for testing
submitting user-defined function. When we first contribute pulsar-functions
to pulsar, we probably didn't clean that up.
The intention behind that change is not including any source code or jar in
the test dependency tree. As including source code would make the testing
function as part of the test dependency, it would volatile the purpose of
testing submitting a user defined function. In this case,
"multifunction.jar" is the a "user-defined" function as the test resource.





>
>
> > > (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.
> >
>
> Sorry for the confusion, that was just an example from a problem I've seen
> before in another project.
>
> --
> Matt Sicker 
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

On Sat, May 12, 2018 at 3:52 PM, Justin Mclean 
wrote:

> Hi,
>
> Sorry but it’s -1 binding due to compiled code in source release.
>


Can anyone point me the ASF policy page about this - "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
>
>

Re: [VOTE] Pulsar 1.22.0-incubating Release Candidate 3

[Sijie Guo]

+1

* the distributions looks good (checked md5, sha, asc)
* test the binary distribution: standalone, run examples
* src distribution looks good: compile, unit tests, run standalone and
examples.

Verified at MacOS 10.13.1

- Sijie


On Sun, Feb 25, 2018 at 3:42 PM, Jai Asher  wrote:

> Kindly ignore the previous message sent on the same subject since it
> contained the wrong dates.
> ==
>
> 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 Thursday, March 1, 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-1010/
>
> The tag to be voted upon:
> v1.22.0-incubating-candidate-3 (5d14788e510faec23fd8ed189ed343e93b489dda)
> https://github.com/apache/incubator-pulsar/releases/tag/
> v1.22.0-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 source package, and follow the README to build
> and run the Pulsar standalone service.
>

Re: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

[Sijie Guo]

+1

On Wed, Jun 28, 2017 at 8:25 AM, John D. Ament 
wrote:

> I have no idea why this is copying both public and private lists.
>
> I'm +1 to graduate.
>
> On Wed, Jun 28, 2017 at 8:06 AM Flavio Junqueira  wrote:
>
> > The Apache DistributedLog community has voted to graduate the project and
> > make it a subproject of Apache BookKeeper. The Apache BookKeeper PMC has
> > also voted to accept DistributedLog as a subproject. The links to the
> vote
> > threads are the following:
> >
> > DistributedLog PPMC vote:
> >
> > https://mail-search.apache.org/members/private-arch/
> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> > <
> > https://mail-search.apache.org/members/private-arch/
> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> > >
> >
> > https://mail-search.apache.org/members/private-arch/
> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=
> ts87rzhpsm096r...@mail.gmail.com%3e
> > <
> > https://mail-search.apache.org/members/private-arch/
> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=
> ts87rzhpsm096r...@mail.gmail.com%3e
> > >
> >
> > DistributedLog Community vote:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> > <
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> > >
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
> TQgqwJs=c...@mail.gmail.com%3e
> > <
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
> TQgqwJs=c...@mail.gmail.com%3e
> > >
> >
> > BookKeeper PMC vote:
> >
> > https://mail-search.apache.org/members/private-arch/
> bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
> htnofojot5rxmv6...@mail.gmail.com%3e
> > <
> > https://mail-search.apache.org/members/private-arch/
> bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
> htnofojot5rxmv6...@mail.gmail.com%3e
> > >
> >
> > https://mail-search.apache.org/members/private-arch/
> bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=
> W=c09qk2...@mail.gmail.com%3e
> > <
> > https://mail-search.apache.org/members/private-arch/
> bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=
> W=c09qk2...@mail.gmail.com%3e
> > >
> >
> > This message is to start an IPMC vote. Please vote on the following:
> >
> > [ ] +1 Graduate Apache DistributedLog from the Incubator.
> > [ ] +0 No opinion
> > [ ] -1 Don't graduate Apache DistributedLog from the Incubator (please
> > provide
> > the reason)
> >
> > This VOTE will be opened for the next 72 hours.
> >
> > -Flavio
>

Re: [VOTE] Heron to enter Apache Incubator

[Sijie Guo]

+1 (non-binding)

- Sijie

On Fri, Jun 16, 2017 at 1:41 PM, Bill Graham  wrote:

> Hi,
>
> Based on the discussion on the incubator mailing list[1] I would like to
> call a vote to add Heron to the Apache Incubator.
>
> The full proposal is available below, and is also available on the Apache
> Incubator wiki at:
> https://wiki.apache.org/incubator/HeronProposal
>
> Please vote:
>   [ ] +1, bring Heron into Incubator
>   [ ] -1, do not bring Heron into Incubator, because...
>
> The vote will open for 7 days until Friday June 23 at 14:00 PT.
>
> Thank you
>
> 1 -
> https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7
> 786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E
>
>
>
> = Heron Proposal =
>
> = Abstract =
> Heron is a real-time, distributed, fault-tolerant stream processing engine
> initially developed by Twitter.
>
> = Proposal =
>
> Heron is a real-time stream processing engine built for high performance,
> ease of manageability, performance predictability and developer
> productivity[1]. We wish to develop a community around Heron to increase
> contributions and see Heron thrive in an open forum.
>
> = Background =
>
> Heron provides the ability for developers to compose directed acyclic
> graphs (DAGs) of real-time query execution logic (i.e. a topology) and
> submit the topology to execute on a pluggable job scheduling system (e.g.,
> Apache Aurora, YARN, Marathon, etc). Users can employ either the native
> Heron API or the Apache Storm API to develop the topology. Heron supports
> the Storm API for ease of migration, but beyond that Heron’s architecture
> differs considerably from Storm’s.
>
> Users submit a topology to the scheduler using the Heron client, which uses
> the Heron binary libraries to deploy all daemons required to run and manage
> the topology. The topology therefore has no reliance on centrally managed
> Heron services, only on a generic job scheduling system, which lends itself
> well to be run on top of Apache Aurora/Mesos or Apache Hadoop/YARN (among
> others).
>
> The scheduler runs each topology as a job consisting of multiple
> containers. One of the containers runs the topology master, responsible for
> managing the topology. The remaining containers each runs a stream manager
> responsible for data routing, a metrics manager that collects and reports
> various metrics and a number of processes called Heron instances which run
> the user-defined logic on the stream of tuples. Parallelism is achieved via
> process-based isolation of Heron instances, which provides predictable
> performance while simplifying debugging. The containers are allocated and
> managed by the scheduler framework based on resource availability of nodes
> in the cluster. The metadata for the topology, such as the physical plan
> and execution details, are stored in the pluggable Heron State Manager
> (e.g. Apache ZooKeeper).
>
> = Rationale =
>
> Heron is a general-purpose, modular and extensible platform that can be
> leveraged to support common, real-time analytics use cases. There is an
> increasing demand for open-source, scalable real-time analytics systems. We
> believe that Heron can be leveraged by other organizations to build
> streaming applications that can benefit from its robustness, high
> performance, adaptability to cloud environments and ease of use. Moreover,
> we hope that open-sourcing Heron will help to further evolve the technology
> as the project attracts contributors with diverse backgrounds and areas of
> expertise.
>
> We believe the Apache foundation is a great fit as the long-term home for
> Heron, as it provides an established process for community-driven
> development and decision making by consensus. This is exactly the model we
> want for future Heron development.
>
> = Initial Goals =
>
>  * Move the existing codebase, website, documentation, and mailing lists to
> Apache-hosted infrastructure.
>  * Integrate with the Apache development process.
>  * Ensure all dependencies are compliant with Apache License version 2.0.
>  * Incrementally develop and release per Apache guidelines.
>
> = Current Status =
>
> Heron is a stable project used in production at Twitter since 2014 and open
> sourced under the ASL v2 license in 2016. The Heron source code is
> currently hosted at github.com (https://github.com/twitter/heron), which
> will seed the Apache git repository.
>
> = Meritocracy =
>
> By submitting this incubator proposal, we’re expressing our intent to build
> a diverse developer community around Heron that will conduct itself
> according to The Apache Way and use a meritocratic means of building it's
> committer base. Several companies and universities have already expressed
> interest in and contributed to Heron. Our goal is to grow the Heron
> community by encouraging open communication, contribution and participation
> of all types, and ensuring that contributors are recognized appropriately.
>
> = Community 

Re: [VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

On Thu, Jun 8, 2017 at 5:47 PM, John D. Ament <johndam...@apache.org> wrote:

> On Thu, Jun 8, 2017 at 8:44 PM Sijie Guo <guosi...@gmail.com> wrote:
>
> > Sure.
> >
> > The discussion email thread between BookKeeper PMC and DistributedLog
> PPMC:
> >
> > https://mail-search.apache.org/pmc/private-arch/
> bookkeeper-private/201706.mbox/%3CCAO2yDyZu+R1EaePyHZuFxe_W0qAkHNYxNnmn5+
> zx6q520uz...@mail.gmail.com%3E
> >
> > The BookKeeper PMC VOTE email thread (it is still ongoing):
> >
> > https://mail-search.apache.org/pmc/private-arch/
> bookkeeper-private/201706.mbox/%3CCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
> htnofojot5rxmv6...@mail.gmail.com%3E
> >
> > As our mentor suggested, I am following the process here :
> > http://incubator.apache.org/guides/graduation.html#subproject
> > This is the community vote for the first step. Let me know if I missed
> > anything.
> >
>
> You mean this is the vote on the PPMC?  If so please drop general@.
>

Yeah, it is the vote on the PPMC. The document is saying to copy the vote
to incubator general list when the VOTE is proposed.

I will drop general@ then.

- Sijie


>
>
> >
> > - Sijie
> >
> >
> >
> > On Thu, Jun 8, 2017 at 5:37 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Sije,
> > >
> > > Can you provide links to the PPMC and PMC votes going on for this move?
> > >
> > > John
> > >
> > > On Thu, Jun 8, 2017 at 8:21 PM Sijie Guo <guosi...@gmail.com> wrote:
> > >
> > > > ( /cc bookkeeper dev@ and incubator general@ for awareness )
> > > >
> > > > Hi all,
> > > >
> > > > There was a joint discussion between BookKeeper PMC and
> DistributedLog
> > > PPMC
> > > > about moving the development of DistributedLog as part of Apache
> > > > BookKeeper. The reasons behind it are:
> > > >
> > > > First, DistributedLog is born as an extension to BookKeeper, to offer
> > > > continuous log streams as the service. The ledger API in bookkeeper
> is
> > a
> > > > lower level API and has learning curves, while the log stream API in
> > > > distributedlog is a higher level API that simplifies the usage. The
> > > > combination of ledger API and stream API would offer a better
> > > > developer/user experience for applications.
> > > >
> > > > Secondly, using ledgers to build continuous (re-openable) log stream
> > is a
> > > > very common pattern for BookKeeper use cases. We did this for HDFS
> > > namenode
> > > > journal, for Hedwig, for DistributedLog, and for Pulsar. The same
> > pattern
> > > > has been implemented again and again. Merge DistributedLog (also
> > > > ManagedLedger in Pulsar) with BookKeeper will consolidate all the
> > > > development efforts around this common 'log stream' pattern.
> > > >
> > > > Thirdly, the 'log' stream abstraction is a good abstraction for both
> > > > messaging and streaming. Internally at BookKeeper, there are a few
> > places
> > > > that can use such 'messaging' facility to improve bookkeeper itself.
> > the
> > > > log stream in DistributedLog can be used internally at bookkeeper for
> > > > streaming changes as well.
> > > >
> > > > We choose merging DistributedLog as subproject rather than modules.
> It
> > > is a
> > > > softer starting point to avoid disrupting the folks who are depending
> > on
> > > > the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
> > > > achieved initial consensus on this merge. There is an official VOTE
> > > ongoing
> > > > in bookkeeper PMC. We'd like to bring this to the distributedlog
> > > community
> > > > for a community vote following the guidelines here
> > > > <http://incubator.apache.org/guides/graduation.html#subproject>.
> > > >
> > > > Please vote +1 if in favor of merging DistributedLog to BookKeeper,
> and
> > > -1
> > > > if not. The vote will be open until Tuesday 13rd June, 18:00 PST.
> > > >
> > > > - Sijie
> > > >
> > >
> >
>

Re: [VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

Sure.

The discussion email thread between BookKeeper PMC and DistributedLog PPMC:
https://mail-search.apache.org/pmc/private-arch/bookkeeper-private/201706.mbox/%3ccao2ydyzu+r1eaepyhzufxe_w0qakhnyxnnmn5+zx6q520uz...@mail.gmail.com%3E

The BookKeeper PMC VOTE email thread (it is still ongoing):
https://mail-search.apache.org/pmc/private-arch/bookkeeper-private/201706.mbox/%3CCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3E

As our mentor suggested, I am following the process here :
http://incubator.apache.org/guides/graduation.html#subproject
This is the community vote for the first step. Let me know if I missed
anything.

- Sijie



On Thu, Jun 8, 2017 at 5:37 PM, John D. Ament <johndam...@apache.org> wrote:

> Sije,
>
> Can you provide links to the PPMC and PMC votes going on for this move?
>
> John
>
> On Thu, Jun 8, 2017 at 8:21 PM Sijie Guo <guosi...@gmail.com> wrote:
>
> > ( /cc bookkeeper dev@ and incubator general@ for awareness )
> >
> > Hi all,
> >
> > There was a joint discussion between BookKeeper PMC and DistributedLog
> PPMC
> > about moving the development of DistributedLog as part of Apache
> > BookKeeper. The reasons behind it are:
> >
> > First, DistributedLog is born as an extension to BookKeeper, to offer
> > continuous log streams as the service. The ledger API in bookkeeper is a
> > lower level API and has learning curves, while the log stream API in
> > distributedlog is a higher level API that simplifies the usage. The
> > combination of ledger API and stream API would offer a better
> > developer/user experience for applications.
> >
> > Secondly, using ledgers to build continuous (re-openable) log stream is a
> > very common pattern for BookKeeper use cases. We did this for HDFS
> namenode
> > journal, for Hedwig, for DistributedLog, and for Pulsar. The same pattern
> > has been implemented again and again. Merge DistributedLog (also
> > ManagedLedger in Pulsar) with BookKeeper will consolidate all the
> > development efforts around this common 'log stream' pattern.
> >
> > Thirdly, the 'log' stream abstraction is a good abstraction for both
> > messaging and streaming. Internally at BookKeeper, there are a few places
> > that can use such 'messaging' facility to improve bookkeeper itself. the
> > log stream in DistributedLog can be used internally at bookkeeper for
> > streaming changes as well.
> >
> > We choose merging DistributedLog as subproject rather than modules. It
> is a
> > softer starting point to avoid disrupting the folks who are depending on
> > the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
> > achieved initial consensus on this merge. There is an official VOTE
> ongoing
> > in bookkeeper PMC. We'd like to bring this to the distributedlog
> community
> > for a community vote following the guidelines here
> > <http://incubator.apache.org/guides/graduation.html#subproject>.
> >
> > Please vote +1 if in favor of merging DistributedLog to BookKeeper, and
> -1
> > if not. The vote will be open until Tuesday 13rd June, 18:00 PST.
> >
> > - Sijie
> >
>

[VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

( /cc bookkeeper dev@ and incubator general@ for awareness )

Hi all,

There was a joint discussion between BookKeeper PMC and DistributedLog PPMC
about moving the development of DistributedLog as part of Apache
BookKeeper. The reasons behind it are:

First, DistributedLog is born as an extension to BookKeeper, to offer
continuous log streams as the service. The ledger API in bookkeeper is a
lower level API and has learning curves, while the log stream API in
distributedlog is a higher level API that simplifies the usage. The
combination of ledger API and stream API would offer a better
developer/user experience for applications.

Secondly, using ledgers to build continuous (re-openable) log stream is a
very common pattern for BookKeeper use cases. We did this for HDFS namenode
journal, for Hedwig, for DistributedLog, and for Pulsar. The same pattern
has been implemented again and again. Merge DistributedLog (also
ManagedLedger in Pulsar) with BookKeeper will consolidate all the
development efforts around this common 'log stream' pattern.

Thirdly, the 'log' stream abstraction is a good abstraction for both
messaging and streaming. Internally at BookKeeper, there are a few places
that can use such 'messaging' facility to improve bookkeeper itself. the
log stream in DistributedLog can be used internally at bookkeeper for
streaming changes as well.

We choose merging DistributedLog as subproject rather than modules. It is a
softer starting point to avoid disrupting the folks who are depending on
the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
achieved initial consensus on this merge. There is an official VOTE ongoing
in bookkeeper PMC. We'd like to bring this to the distributedlog community
for a community vote following the guidelines here
.

Please vote +1 if in favor of merging DistributedLog to BookKeeper, and -1
if not. The vote will be open until Tuesday 13rd June, 18:00 PST.

- Sijie

Re: [VOTE] Pulsar into the Apache Incubator

[Sijie Guo]

+1 (non-binding)

Great to see Pulsar joining the ASF and more and more projects are built
over Apache BookKeeper!

- Sijie

On Tue, May 16, 2017 at 7:39 PM, Bryan Call  wrote:

> Hi All,
>
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which
> only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/PulsarProposal
>
> -Bryan
>
>
> = Pulsar Proposal =
>
> == Abstract ==
>
> 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.
>
> == Proposal ==
>
> Pub-sub messaging is a very common design pattern that is increasingly
> found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average
> and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability,
> and
> delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
>
> Pulsar has been developed at Yahoo to address these specific requirements
> by
> providing a hosted service supporting millions of topics for multiple
> tenants.
> The current incarnation of Pulsar has been open-sourced under Apache
> license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
>
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics
> while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
>
> Since the open sourcing of Pulsar, the development has been done
> exclusively
> on the public Github repository and two major releases were shipped (1.15
> and
> 1.16), along with multiple minor ones. Several other companies have
> expressed
> interest in the project and its future direction.
>
> == Rationale ==
>
> Pulsar is a platform that is built on top of several other Apache
> projects. In
> particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream
> processing
> solution.
>
> We want to establish a community outside the scope of initial core
> developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the
> model
> we want to adopt for future Pulsar development.
>
> == Initial Goals ==
>
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
>
> == Current Status ==
>
> Pulsar has been in service at large scale for more than 2 years at Yahoo.
> In
> this time around 60 different applications were integrated with Pulsar.
> Other
> companies are evaluating it as well and have been contributing code to the
> project.
>
> === Meritocracy ===
>
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute
> and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to
> all
> contributors.
>
> === Community ===
>
> We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very
> important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the same model and that bringing Pulsar
> to
> Apache will get the community to grow stronger.
>
> === Core Developers ===
>
> Pulsar has been initially developed at Yahoo and received significant
> contributions from Yahoo Japan. After having open-sourced the 

[ANNOUNCE] Apache DistributedLog 0.4.0-incubating Release

[Sijie Guo]

The Apache DistributedLog team would like to announce the release of Apache
DistributedLog 0.4.0-incubating.

Apache DistributedLog (incubating) is a high performance replicated log
store. It provides replicated-log as the storage primitive for building
real-time services. Its serves as a fundamental building block for
distributed applications that requires durability, replication and strong
consistency.

The highlights of 0.4.0-incubating are:

- Refactor the codebase to abstract the core metadata and data operations
for the log store into interfaces. So developers can easily integrate
DistributedLog with other metadata stores like etcd, and integrate
DistributedLog with other cold data stores like HDFS, S3.
- A new read ahead implementation for the log reader to better handle slow
storage nodes.
- Provide the log stream placement policy on the proxy service, to develop
and experiment with different placement policies and integrate with
different auto-scaling mechanisms.

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/distributedlog/0.4.0-incubating/

All JIRAs completed for this release are tagged with 'FixVersion =
0.4.0-incubating'; the JIRA release notes can be found here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320620=12337980

Release notes are available at:

https://distributedlog.incubator.apache.org/docs/latest/start/download

More details regarding Apache DistributedLog (incubating) can be found here:
https://distributedlog.incubator.apache.org/

We thank everyone who made this release possible.

Thanks!
The Apache DistributedLog Team



DISCLAIMER:

Apache DistributedLog 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.

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

There are 3 binding approving votes and 2 non-binding votes, all of which
are following:

binding votes:

- John D. Ament
- Henry Saputra
- Justin Mclean

non-binding votes:

- Ivam Firestone
- Jia Zhai

There are no disapproving votes.

We will proceed with this release as staged.

Thanks everyone!

- Sijie

On Mon, Apr 17, 2017 at 11:55 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Hi all,
>
> Please review and vote on the release candidate #4 for the Apache
> DistributedLog version 0.4.0-incubating, as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3][4],
> * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> * website pull request listing the release [7] and publishing the API
> reference manual.
>
> The Apache DistributedLog community has unanimously approved this release
> [8].
>
> As customary, the vote will be open for at least 72 hours. It is adopted
> by a majority approval with at least three PMC affirmative votes. If
> approved, we will proceed with the release.
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> ersion=12337980==12320620
> [2] https://dist.apache.org/repos/dist/dev/incubator/distrib
> utedlog/0.4.0-incubating-RC4/
> [3] https://repository.apache.org/content/repositories/orgap
> achedistributedlog-1007/
> [4] https://repository.apache.org/content/repositories/orgap
> achedistributedlog-1008/
> [5] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.11
> [6] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.10
> [7] https://github.com/apache/incubator-distributedlog/pull/109
> [8] http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_
> iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

On Mon, Apr 24, 2017 at 6:48 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> Checked the source packages:
> - incubating in name
> - signature and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE are good
> - No unexpected binaries
> - All source files have ASF headers
> - Can compile from source
>
> I did notice two MIT licenses [1][2] but the other than the license files
> there seems to be nothing else included. Are these needed?
>

I think [1][2] are same file. docs/latest is a symlink to the current docs.
the LICENSE.txt file is shipped as part of the jekyll-rst plugin.


>
> The binary LICENSE and NOTICE files need updating as they are bundling
> other licensed products. i.e.aop alliance intercept, bookkeeper, zookeeper,
> apache commons and various twitter GitHub projects.
>

I will create a jira to follow up on this.


>
> Thanks,
> Justin
>
> 1. ./docs/_plugins/jekyll-rst/LICENSE.txt
> 2. ./website/docs/latest/_plugins/jekyll-rst/LICENSE.txt
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [RESULT] [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Thank you Justin!

- Sijie

On Mon, Apr 24, 2017 at 6:52 PM, Justin Mclean 
wrote:

> Hi,
>
> > Oh, my bad. I didn't check that. I was just counting the votes. So we
> need
> > one more binding vote for approving this release?
>
> You now have one more binding vote so can release.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [RESULT] [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Oh, my bad. I didn't check that. I was just counting the votes. So we need
one more binding vote for approving this release?

- Sijie

On Mon, Apr 24, 2017 at 5:11 PM, John D. Ament <johndam...@apache.org>
wrote:

> Sijie,
>
> I can't find anyone by the name of Ivam Firestone on the IPMC.  Please
> double check your binding votes.
>
> http://home.apache.org/phonebook.html?ctte=incubator
>
> John
>
> On Mon, Apr 24, 2017 at 6:44 PM Sijie Guo <guosi...@gmail.com> wrote:
>
> > There are 3 binding approving votes, all of which are following:
> >
> > - Ivam Firestone
> > - John D. Ament
> > - Henry Saputra
> >
> > There are no disapproving votes.
> >
> > We will proceed with this release as staged.
> >
> > Thanks everyone!
> >
> > - Sijie
> >
> >
> >
> > On Mon, Apr 17, 2017 at 11:55 PM, Sijie Guo <guosi...@gmail.com> wrote:
> >
> > > Hi all,
> > >
> > > Please review and vote on the release candidate #4 for the Apache
> > > DistributedLog version 0.4.0-incubating, as follows:
> > >
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > The complete staging area is available for your review, which includes:
> > >
> > > * JIRA release notes [1],
> > > * the official Apache source release to be deployed to
> > dist.apache.org
> > >  [2],
> > > * all artifacts to be deployed to the Maven Central Repository
> > [3][4],
> > > * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> > > "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> > > * website pull request listing the release [7] and publishing the
> API
> > > reference manual.
> > >
> > > The Apache DistributedLog community has unanimously approved this
> release
> > > [8].
> > >
> > > As customary, the vote will be open for at least 72 hours. It is
> adopted
> > > by a majority approval with at least three PMC affirmative votes. If
> > > approved, we will proceed with the release.
> > >
> > > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> > > ersion=12337980==12320620
> > > [2] https://dist.apache.org/repos/dist/dev/incubator/distrib
> > > utedlog/0.4.0-incubating-RC4/
> > > [3] https://repository.apache.org/content/repositories/orgap
> > > achedistributedlog-1007/
> > > [4] https://repository.apache.org/content/repositories/orgap
> > > achedistributedlog-1008/
> > > [5] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.11
> > > [6] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.10
> > > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > > [8] http://mail-archives.apache.org/mod_mbox/incubator-
> > > distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_
> > > iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E
> > >
> >
>

[RESULT] [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

There are 3 binding approving votes, all of which are following:

- Ivam Firestone
- John D. Ament
- Henry Saputra

There are no disapproving votes.

We will proceed with this release as staged.

Thanks everyone!

- Sijie



On Mon, Apr 17, 2017 at 11:55 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Hi all,
>
> Please review and vote on the release candidate #4 for the Apache
> DistributedLog version 0.4.0-incubating, as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3][4],
> * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> * website pull request listing the release [7] and publishing the API
> reference manual.
>
> The Apache DistributedLog community has unanimously approved this release
> [8].
>
> As customary, the vote will be open for at least 72 hours. It is adopted
> by a majority approval with at least three PMC affirmative votes. If
> approved, we will proceed with the release.
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> ersion=12337980==12320620
> [2] https://dist.apache.org/repos/dist/dev/incubator/distrib
> utedlog/0.4.0-incubating-RC4/
> [3] https://repository.apache.org/content/repositories/orgap
> achedistributedlog-1007/
> [4] https://repository.apache.org/content/repositories/orgap
> achedistributedlog-1008/
> [5] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.11
> [6] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.10
> [7] https://github.com/apache/incubator-distributedlog/pull/109
> [8] http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_
> iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Thank you all. Can any IPMC member help review and vote this?

Sijie

On Apr 19, 2017 4:47 AM, "Jia Zhai" <zhaiji...@gmail.com> wrote:

> +1(non-binding)
> - verified packages (md5, asc and sha1 all look good)
> - the source package build and test all run successfully.
> - NOTICE, DISCLAIMER, License headers look good.
>
> On Tue, Apr 18, 2017 at 8:36 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > +1 to release
> >
> > - NOTICE file looks fine
> > - Source headers look correct
> > - DISCLAIMER present.
> >
> > On Tue, Apr 18, 2017 at 2:55 AM Sijie Guo <guosi...@gmail.com> wrote:
> >
> > > Hi all,
> > >
> > > Please review and vote on the release candidate #4 for the Apache
> > > DistributedLog version 0.4.0-incubating, as follows:
> > >
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > The complete staging area is available for your review, which includes:
> > >
> > > * JIRA release notes [1],
> > > * the official Apache source release to be deployed to
> > dist.apache.org
> > >  [2],
> > > * all artifacts to be deployed to the Maven Central Repository
> > [3][4],
> > > * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> > > "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> > > * website pull request listing the release [7] and publishing the
> API
> > > reference manual.
> > >
> > > The Apache DistributedLog community has unanimously approved this
> release
> > > [8].
> > >
> > > As customary, the vote will be open for at least 72 hours. It is
> adopted
> > > by a
> > > majority approval with at least three PMC affirmative votes. If
> approved,
> > > we
> > > will proceed with the release.
> > >
> > > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> > > ersion=12337980==12320620
> > > [2] https://dist.apache.org/repos/dist/dev/incubator/
> > distributedlog/0.4.0-
> > > incubating-RC4/
> > > <https://dist.apache.org/repos/dist/dev/incubator/
> distributedlog/0.4.0-
> > incubating-RC4/>
> > > [3] https://repository.apache.org/content/repositories/
> > > orgapachedistributedlog-1007/
> > > [4] https://repository.apache.org/content/repositories/
> > > orgapachedistributedlog-1008/
> > > [5] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.11
> > > [6] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.10
> > > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > > [8]
> > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-
> > distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_
> > iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E
> > >
> >
>

[VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Hi all,

Please review and vote on the release candidate #4 for the Apache
DistributedLog version 0.4.0-incubating, as follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
 [2],
* all artifacts to be deployed to the Maven Central Repository [3][4],
* source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
* website pull request listing the release [7] and publishing the API
reference manual.

The Apache DistributedLog community has unanimously approved this release
[8].

As customary, the vote will be open for at least 72 hours. It is adopted by a
majority approval with at least three PMC affirmative votes. If approved, we
will proceed with the release.

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
ersion=12337980==12320620
[2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC4/
[3] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1007/
[4] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1008/
[5] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC4_2.11
[6] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC4_2.10
[7] https://github.com/apache/incubator-distributedlog/pull/109
[8]
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Awesome. I learned a lot from this discussion. We will address these
comments and call another vote.

- Sijie

On Mon, Apr 10, 2017 at 3:11 PM, Marvin Humphrey 
wrote:

> On Mon, Apr 10, 2017 at 2:28 PM, Henry Saputra 
> wrote:
> > The question is whether we need to keep this section:
> >
> > Portions of this software were developed by Twitter.
> > Copyright Twitter, 2017
> >
> > in the NOTICE file. Since Twitter already signed off the source
> > contributions, we could probably remove this section.
>
> Only Twitter's authorized representative may legally remove Twitter's
> copyright notice.  Everyone else must leave it alone.
>
> Unless something unusual has occurred (like a new SGA from Twitter in
> 2017),
> there should not have been a need to update Twitter's copyright.  Josh was
> right to flag that as weird.
>
> Sijie, I see that it was your commit that changed the copyright year in
> NOTICE.  It was correct to update the ASF copyright, so please leave that
> as
> 2017 (and continue to updated it in future years).  For the Twitter
> copyright,
> please either restore the 2016 date or discuss any unusual circumstances.
> (Feel free to ask questions, we're here to help.)
>
> Josh was also right to flag the addition of the "Copyright 2017 The Apache
> Software Foundation" notices in source headers.
>
> http://www.apache.org/legal/src-headers.html#headers
>
> 2. Each source file should include the following license header -- note
>that there should be no copyright notice in the header:
>
> For individual files, contributors continue to hold copyright on their
> contributions.  The ASF (unlike some other entities such as the FSF) does
> not
> require copyright assignment.  Thus the ASF only holds copyright in the
> collection; that's what's expressed in the NOTICE file ASF copyright
> notice.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Thank you, Josh. Will address your comments.

On Sun, Apr 9, 2017 at 4:38 PM, Josh Elser <els...@apache.org> wrote:

> -1 (binding) your source releases still do not contain the DISCLAIMER file
> that John pointed out in rc2 [1].
>
> * mvn apache-rat:check fails on `src/main/resources/DISCLAIMER.bin.txt`

* Don't include 'Copyright 2017 The Apache Software Foundation' in the
> license headers of your source files. The NOTICE files sufficiently covers
> this?

* Is the 'Copyright Twitter, 2017' accurate? DistributedLog has been
> incubating since 2016, right? Have you included new IP from Twitter since
> then?
>

DLog has been incubating since 2016. But we were asked to update the year
in the NOTICE to 2017 in last vote. My question for this is: should the
year be the year we started incubating or the year when this release is
released? I heard different things from different places.

- Sijie


>
> * sigs/xsums OK
> * Can build source releases
>
> - Josh
>
> [1] https://lists.apache.org/thread.html/c8694114552717fa4776b54
> 1406c2e294a4c654721647bac86340f3a@%3Cgeneral.incubator.apache.org%3E
>
>
> Sijie Guo wrote:
>
>> Hi everyone,
>>
>> Please review and vote on the release candidate #3 for the Apache
>> DistributedLog version 0.4.0-incubating, as follows:
>>  [ ] +1, Approve the release
>>  [ ] -1, Do not approve the release (please provide specific comments)
>>
>> The complete staging area is available for your review, which includes:
>>
>>  * JIRA release notes [1],
>>  * the official Apache source release to be deployed to
>> dist.apache.org
>>   [2],
>>  * all artifacts to be deployed to the Maven Central Repository [3],
>>  * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
>> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
>>  * website pull request listing the release [6] and publishing the API
>> reference manual.
>>
>> The Apache DistributedLog community has unanimously approved this release
>> [7].
>>
>> As customary, the vote will be open for at least 72 hours. It is adopted
>> by a
>> majority approval with at least three PMC affirmative votes. If approved,
>> we
>> will proceed with the release.
>>
>> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> version=12337980==12320620
>> [2] https://dist.apache.org/repos/dist/dev/incubator/distributed
>> log/0.4.0-
>> incubating-RC3/
>> [3] https://repository.apache.org/content/repositories/
>> orgapachedistributedlog-1006/
>> [4] https://github.com/apache/incubator-distributedlog/tree/
>> v0.4.0-incubating-RC3_2.11
>> [5] https://github.com/apache/incubator-distributedlog/tree/
>> v0.4.0-incubating-RC3_2.10
>> [6] https://github.com/apache/incubator-distributedlog/pull/109
>> [7]
>> http://mail-archives.apache.org/mod_mbox/incubator-distribut
>> edlog-dev/201704.mbox/%3CCAO2yDyY7DxeQ0Xnm9sPmXTjwF_yhc8nAHN
>> %2B4VxmD7jjGbyoGjQ%40mail.gmail.com%3E
>>
>>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Hi everyone,

Please review and vote on the release candidate #3 for the Apache
DistributedLog version 0.4.0-incubating, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
 [2],
* all artifacts to be deployed to the Maven Central Repository [3],
* source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
* website pull request listing the release [6] and publishing the API
reference manual.

The Apache DistributedLog community has unanimously approved this release
[7].

As customary, the vote will be open for at least 72 hours. It is adopted by a
majority approval with at least three PMC affirmative votes. If approved, we
will proceed with the release.

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
version=12337980==12320620
[2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC3/
[3] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1006/
[4] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC3_2.11
[5] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC3_2.10
[6] https://github.com/apache/incubator-distributedlog/pull/109
[7]
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201704.mbox/%3CCAO2yDyY7DxeQ0Xnm9sPmXTjwF_yhc8nAHN%2B4VxmD7jjGbyoGjQ%40mail.gmail.com%3E

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

On Sat, Jan 28, 2017 at 8:39 AM, Sijie Guo <si...@apache.org> wrote:

>
>
> On Fri, Jan 27, 2017 at 11:37 PM, Justin Mclean <jus...@classsoftware.com>
> wrote:
>
>> Hi,
>>
>> > I think they might come from apache bookkeeper. when we started building
>> > DL, we might copy some headers from bookkeeper. We will address this in
>> > next RC.
>>
>> Look like they may of also fixed this issue [1]. For why see the last bit
>> of Step 2 here [2]. I assume there’s no code from bookkeeper included in
>> the source release?
>>
>
> Correct. We will follow [2] to fix this one.
>
>
>>
>> > Oh the service and benchmark are two modules in the maven project. What
>> is
>> > your suggestion for this? Shall we create a giant binary package inckude
>> > both modules?
>>
>> I would of expected the source when compiled produces those artefacts.
>>
>
> When the source is compiled with 'mvn package', there will be two binary
> packages produced (service & benchmark). So that's how the binary packages
> were produced. I am not sure if this can address your concern here.
>

FYI.

This is the step how we generated the packages (we use maven release
plugin) -
https://github.com/apache/incubator-distributedlog/pull/51/files#diff-51315afca7c712ad9ce48f7ebb5c042fR228

This is the step how we copy the generated packages to stage them -
https://github.com/apache/incubator-distributedlog/pull/51/files#diff-51315afca7c712ad9ce48f7ebb5c042fR246



>
>
>>
>> Not sure what the solution is here as It’s a little unclear me where
>> ether source for those modules comes from. I assume it form the source
>> release?
>>
>
> Correct.
>
>
>>
>> Thanks,
>> Justin
>>
>> 1. https://issues.apache.org/jira/browse/BOOKKEEPER-976
>> 2. https://www.apache.org/legal/src-headers.html#headers
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

On Fri, Jan 27, 2017 at 11:37 PM, Justin Mclean 
wrote:

> Hi,
>
> > I think they might come from apache bookkeeper. when we started building
> > DL, we might copy some headers from bookkeeper. We will address this in
> > next RC.
>
> Look like they may of also fixed this issue [1]. For why see the last bit
> of Step 2 here [2]. I assume there’s no code from bookkeeper included in
> the source release?
>

Correct. We will follow [2] to fix this one.


>
> > Oh the service and benchmark are two modules in the maven project. What
> is
> > your suggestion for this? Shall we create a giant binary package inckude
> > both modules?
>
> I would of expected the source when compiled produces those artefacts.
>

When the source is compiled with 'mvn package', there will be two binary
packages produced (service & benchmark). So that's how the binary packages
were produced. I am not sure if this can address your concern here.


>
> Not sure what the solution is here as It’s a little unclear me where ether
> source for those modules comes from. I assume it form the source release?
>

Correct.


>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/BOOKKEEPER-976
> 2. https://www.apache.org/legal/src-headers.html#headers
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Hello, Justin,

Thank you so much for you feedback.

On Jan 26, 2017 6:26 PM, "Justin Mclean"  wrote:

Hi,

I also be -1 binding on this due to missing DISCLAIMER, ASF header issues
and a possible binary release issue.

I checked:
- name includes incubating
- signatures good
- DISCLAIMER is missing
- License is OK
- Year needs updating in NOTICE.
- A large number of files seem to have have incorrect ASF headers with a
copyright line "Copyright 2007 The Apache Software Foundation”. Did this
come from somewhere else?


I think they might come from apache bookkeeper. when we started building
DL, we might copy some headers from bookkeeper. We will address this in
next RC.

- Can compile from source

If you are creating convenience binaries then the compiled code in them
must match the code from the source release. It’s not clear to me how the
benchmark and service binaries relate to the source release. [1]


Oh the service and benchmark are two modules in the maven project. What is
your suggestion for this? Shall we create a giant binary package inckude
both modules?

Thank you!

Sijie


Thanks,
Justin

1. http://www.apache.org/legal/release-policy.html#compiled-packages
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

On Thu, Jan 26, 2017 at 6:06 AM, John D. Ament <johndam...@apache.org>
wrote:

> Its not clear if you intended this to be the IPMC vote or the dev vote.
>

Sorry. it is my first time doing incubator project release. If I made
something wrong, please let me know.

This is vote is intended to for the IPMC vote.


>
> -1 Since the release does not include the DISCLAIMER file and README does
> not include the DISCLAIMER text (either would be fine per policy, but
> generally we look for DISCLAIMER).
>

Gotcha. We will try to add this.


>
> There were no binaries in the source.


The source package only includes source codes. The binaries are shipped as
two separated packages, one is service package, the other one is benchmark
package. Is there a policy about packaging?


> NOTICE should be updated for 2017.
>

Will update this.


> I'm not sure why the NOTICE includes Hadoop references.  Do you still ship
> modified versions?
>

Ah, here is the discussion about the NOTICE includes Hadoop references.
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201701.mbox/browser

I think we are following what other projects were doing when we are making
a similar code change. And there is a JIRA to follow up after this release.
Do you see a major concern here? If so, we will address it in the new RC.

Thanks,

Sijie



>
> On Thu, Jan 26, 2017 at 1:36 AM Sijie Guo <si...@apache.org> wrote:
>
> >   Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the Apache
> > DistributedLog version 0.4.0-incubating, as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> >
> > The complete staging area is available for your review, which
> includes:
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org
> > [2],
> > * all artifacts to be deployed to the Maven Central Repository
> [3][4],
> > * source code tag "v0.4.0-RC0" [4],
> > * code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> > "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
> > * website pull request listing the release [7] and publishing the API
> > reference manual.
> >
> > The Apache DistributedLog community has unanimously approved this
> > release [8].
> >
> > As customary, the vote will be open for at least 72 hours. It is
> > adopted by
> > a majority approval with at least three PMC affirmative votes. If
> > approved,
> > we will proceed with the release.
> >
> > Thanks!
> >
> > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> > rojectId=12320620=12337980
> > [2] https://dist.apache.org/repos/dist/dev/incubator/
> distributedlog/0.4.0-
> > incubating-RC2/
> > <https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC2/>
> > [3] https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1003/
> > [4] https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1004/
> > [5] https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC1_2.11
> > [6] https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC1_2.10
> > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > [8]
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201701.mbox/%3CCAO2yDyYwQgg%3DSRuBdxTPC%
> 3DT3bkZO4O0EULwq9tUB_Uno01XW7A%40mail.gmail.com%3E
> >
>

[VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

  Hi everyone,

Please review and vote on the release candidate #2 for the Apache
DistributedLog version 0.4.0-incubating, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
[2],
* all artifacts to be deployed to the Maven Central Repository [3][4],
* source code tag "v0.4.0-RC0" [4],
* code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
* website pull request listing the release [7] and publishing the API
reference manual.

The Apache DistributedLog community has unanimously approved this
release [8].

As customary, the vote will be open for at least 72 hours. It is
adopted by
a majority approval with at least three PMC affirmative votes. If
approved,
we will proceed with the release.

Thanks!

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
rojectId=12320620=12337980
[2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC2/
[3] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1003/
[4] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1004/
[5] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC1_2.11
[6] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC1_2.10
[7] https://github.com/apache/incubator-distributedlog/pull/109
[8]
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201701.mbox/%3CCAO2yDyYwQgg%3DSRuBdxTPC%3DT3bkZO4O0EULwq9tUB_Uno01XW7A%40mail.gmail.com%3E

[RESULT] [VOTE] Accept DistributedLog into the Apache Incubator

[Sijie Guo]

The results are in and voting is now closed. The votes were ...

[15] +1 Accept DistributedLog into the Apache Incubator

Sijie Guo
Jia Zhai
Naresh Agarwal
Debo Dutta
Tsuyoshi (ozawa@)
Flavio Junqueira (binding)
Chris Douglas (binding)
Henry Saputra (binding)
Josh Elser (binding)
Mahak Patidar
Dave Rusek
Stevo Slavic
Chris Nauroth (binding)
Suneel Marthi (binding)
Jakob Homan (binding)

[0] +0 Abstain.
[0] -1 Do not accept DistributedLog into the Apache Incubator because ...

DistributedLog has been accepted into the Incubator!

Thanks everyone who took time to look at the project and vote!

The vote thread can be found there:

http://mail-archives.apache.org/mod_mbox/incubator-general/201606.mbox/%3CCAO2yDyamYeMZ892GdwjxGn_J-WKgUcOLqfudA4YyU4nqZVmaKA%40mail.gmail.com%3E


-- Forwarded message --
From: Sijie Guo <si...@apache.org>
Date: Mon, Jun 20, 2016 at 10:11 PM
Subject: [VOTE] Accept DistributedLog into the Apache Incubator
To: general@incubator.apache.org


Hello All,

Following the discussion thread, I would like to call a VOTE on accepting
DistributedLog into the Apache Incubator.

[] +1 Accept DistributedLog into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept DistributedLog into the Apache Incubator because ...

This vote will be open for at least 72 hours.

The proposal follows, you can also access the wiki page:
https://wiki.apache.org/incubator/DistributedLogProposal

Here is my +1.

Thanks,
Sijie

= Abstract =
DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a
fundamental building block for building reliable distributed systems, e.g
replicated-state-machines, general pub/sub systems, distributed databases,
distributed queues and etc.

See “Building Distributedlog - Twitter’s high performance replicated log
service” for details:
https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service

= Proposal =
We propose to contribute DistributedLog codebase and associated artifacts
(e.g. documentation, web-site content etc.) to the Apache Software
Foundation with the intent of forming a productive, meritocratic and open
community around DistributedLog’s continued development, according to the
‘Apache Way’.

= Background =
Engineers at Twitter began developing DistributedLog in early 2013.
DistributedLog is described in a Twitter engineering blog post and
presented at the Messaging Meetup in Sep 2015. It has been released as an
Apache-licensed open-source project on GitHub in May 2016.

DistributedLog is a high-performance replicated log service, which provides
simple stream-oriented abstractions over log-segments and offers
durability, replication and strong consistency for building reliable
distributed systems. The features offered by DistributedLog includes:

 * Simple high-level, stream oriented interface
 * Naming and metadata scheme for managing streams and other entities
 * Log data management policies, include data segmentation and data
retention
 * Fast write pipeline leveraging batching and compression
 * Fast read mechanism leveraging long-poll and read-ahead caching
 * Service tiers supporting writer fan-in and reader fan-out
 * Geo-replicated logs

DistributedLog’s most important benefit is high-performance with a strong
durability guarantee, making it extremely appropriate for running different
workloads from distributed database journaling to real-time stream
computing. Its modern, layered architecture makes it easy to run the
service tiers in multi-tenant datacenter environments such as Apache Mesos
or cloud environments such as EC2.

= Rationale =
DistributedLog is designed to provide core fundamental features like
high-performance, durability and strong consistency to anyone who is
building reliable distributed systems, in a simple and efficient way.

We believe that the ASF is the right venue to foster an open-source
community around DistributedLog’s development. We expect that
DistributedLog will benefit from collaboration with related Apache
projects, and under the auspices of the ASF will attract talented
contributors who will push DistributedLog’s development forward at a faster
pace.

We believe that the timing is right for DistributedLog’s development to
move to the ASF: DistributedLog has already run in production at Twitter
for 3 years and served various workloads including a distributed database
journal, reliable cross datacenter replication, search ingestion,
andgeneral pub/sub messaging. The project is stable. We are excited to see
where an ASF-based community can take DistributedLog.

= Current Status =
DistributedLog is a stable project that has been used in production at
Twitter for 3 years. The source code is public at github.com/twitter, which
will seed the Apache git repository.

= Meritocracy =
We understand the central importance of meritocracy to the Apache Way. We
will work to establish a welcoming

[VOTE] Accept DistributedLog into the Apache Incubator

[Sijie Guo]

:

 * DistributedLog stores log segments as Ledgers in Apache BookKeeper.
 * DistributedLog uses Apache ZooKeeper for naming and metadata management
and tracking the ownership of logs.
 * DistributedLog uses Apache Thrift as its RPC and serialization framework.
 * In the long-term, DistributedLog’s data will be stored in Apache Hadoop
clusters powered by HDFS filesystem for archives and backup.

= Known Risks =
== Orphaned Products ==
DistributedLog is used as the fundamental messaging infrastructure at
Twitter. It has been serving production traffic for online database
systems, search ingestion and a general pub/sub system. Twitter remains
committed to developing and supporting the project. Twitter has a strong
track record in standing behind projects that were contributed to the ASF
by its employees, including Apache Mesos, Apache Aurora, Apache BookKeeper,
Apache Hadoop. There are many companies are interested in using it in
production.

== Inexperience with Open Source ==
The core developers of DistributedLog are committers of Apache BookKeeper.
Although other committers on the initial list are committers or have less
experience with the ASF, they already are active in Apache BookKeeper
community. We are confident that the project can be run in accordance with
Apache principles on an ongoing basis.

== Homogeneous Developers ==
The initial committers are from Twitter. We hope to encourage contributions
from other developers and grow them into committers after they have had
time to continue their contributions.

== Reliance on Salaried Developers ==
Many of DistributedLog’s initial set of committers work full-time on
DistributedLog, and are paid to do so. However, as mentioned elsewhere, we
anticipate growth in the developer community which we hope will include
people from industry, hobbyists, and academics who have an interested in
distributed messaging systems.

== Relationships with Other Apache Products ==
DistributedLog uses Apache BookKeeper to store log segments and Apache
ZooKeeper to store log metadata and manage log namespaces. It provides an
end-to-end solution for replicated logs, to make building reliable
distributed systems much easier. Unlike Kafka or ActiveMQ, DistributedLog
is not a full-fledged pub/sub, queuing or messaging system.  Instead, it is
targeting on providing a fundamental building block for other distributed
systems, offering durability, replication and consistency. So it could be
used by other distributed systems, such as transactional log for replicated
state machines (e.g., HDFS NameNode), WAL for distributed databases (e.g.
HBase), Journal for in-memory services (e.g., Kestrel) and even storage
backend for a full-fledged messaging system.

== An Excessive Fascination with the Apache Brand ==
DistributedLog builds on two existing top-level projects, Apache BookKeeper
and Apache ZooKeeper. Some of the core developers actively participate in
both projects and understand well the implications of being hosted by
Apache. We would like this project to build on the same core values of ASF
and to grow a community based on meritocracy. Also, there are several other
projects already hosted by ASF in this space of reliable messaging and that
overlap with DistributedLog in interests and scope. Consequently, the
combination of all these observations makes us believe that DistributedLog
should be hosted by the ASF.

= Documentation =
Building DistributedLog: Twitter’s high performance replicated log service (
https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
)

Documentation located in http://distributedlog.io.

= Initial Source =
DistributedLog’s initial source contribution will come from
http://github.com/twitter/distributedlog/.

= External Dependencies =
DistributedLog depends upon a number of third-party libraries, which we
list below.

 * Apache BookKeeper (Apache Software License v2.0)
 * Apache Commons (Apache Software License v2.0)
 * Apache Maven (Apache Software License v2.0)
 * Apache Thrift (Apache Software License v2.0)
 * Apache ZooKeeper (Apache Software License v2.0)
 * Google Guava (Apache Software License v2.0)
 * Mockito (MIT License)
 * Junit (Eclipse Public License 1.0)
 * LZ4-java (Apache Software License v2.0)
 * SLF4J (MIT License)
 * Twitter Finagle (Apache Software License v2.0)
 * Twitter Scrooge (Apache Software License v2.0)
 * Twitter Util (Apache Software License v2.0)

= Required Resources =
We request that following resources be created for the project to use:

== Mailing lists ==
 * priv...@distributedlog.incubator.apache.org (moderated subscriptions)
 * comm...@distributedlog.incubator.apache.org
 * d...@distributedlog.incubator.apache.org
 * u...@distributedlog.incubator.apache.org

== Git repository ==
https://git.apache.org/distributedlog.git

== JIRA instance ==
JIRA project DLOG (DLOG or DL)

= Initial Committers =
 * Sijie Guo (Apache BookKeeper Committer, Twitter)
 * Robin Dhamankar (Apache BookKeeper

Re: [DISCUSS] DistributedLog Incubation Proposal

[Sijie Guo]

Any feedback here, folks? If no, I'd like to start a voting thread soon.

- Sijie

On Wed, Jun 8, 2016 at 9:34 PM, Sijie Guo <si...@apache.org> wrote:

> Hi,
>
> I would like to propose DistributedLog to be an Apache Incubator project.
>
> DistributedLog is a high performance replicated log service.
> It offers durability, replication and strong consistency, which provides
> a fundamental building block for building reliable distributed systems,
> e.g replicated-state-machines, general pub/sub systems, distributed
> databases, distributed queues and etc.
>
> Here's a link to the proposal in the Incubator wiki
>
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> I've also pasted the initial contents below.
>
> Thanks,
>
> Sijie
>
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers 
> durability, replication and strong consistency, which provides a fundamental 
> building block for building reliable distributed systems, e.g 
> replicated-state-machines, general pub/sub systems, distributed databases, 
> distributed queues and etc.
>
> See “Building Distributedlog - Twitter’s high performance replicated log 
> service” for details: 
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts 
> (e.g. documentation, web-site content etc.) to the Apache Software Foundation 
> with the intent of forming a productive, meritocratic and open community 
> around DistributedLog’s continued development, according to the ‘Apache Way’.
>
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013. 
> DistributedLog is described in a Twitter engineering blog post and presented 
> at the Messaging Meetup in Sep 2015. It has been released as an 
> Apache-licensed open-source project on GitHub in May 2016.
>
> DistributedLog is a high-performance replicated log service, which provides 
> simple stream-oriented abstractions over log-segments and offers durability, 
> replication and strong consistency for building reliable distributed systems. 
> The features offered by DistributedLog includes:
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
>
> DistributedLog’s most important benefit is high-performance with a strong 
> durability guarantee, making it extremely appropriate for running different 
> workloads from distributed database journaling to real-time stream computing. 
> Its modern, layered architecture makes it easy to run the service tiers in 
> multi-tenant datacenter environments such as Apache Mesos or cloud 
> environments such as EC2.
>
> = Rationale =
> DistributedLog is designed to provide core fundamental features like 
> high-performance, durability and strong consistency to anyone who is building 
> reliable distributed systems, in a simple and efficient way.
>
> We believe that the ASF is the right venue to foster an open-source community 
> around DistributedLog’s development. We expect that DistributedLog will 
> benefit from collaboration with related Apache projects, and under the 
> auspices of the ASF will attract talented contributors who will push 
> DistributedLog’s development forward at a faster pace.
>
> We believe that the timing is right for DistributedLog’s development to move 
> to the ASF: DistributedLog has already run in production at Twitter for 3 
> years and served various workloads including a distributed database journal, 
> reliable cross datacenter replication, search ingestion, andgeneral pub/sub 
> messaging. The project is stable. We are excited to see where an ASF-based 
> community can take DistributedLog.
>
> = Current Status =
> DistributedLog is a stable project that has been used in production at 
> Twitter for 3 years. The source code is public at github.com/twitter, which 
> will seed the Apache git repository.
>
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We 
> will work to establish a welcoming, fair and meritocratic community. Several 
> companies have already expressed interest in this project, and we intend to 
> invite additional developers to participate. We look forward to growing a 
> rich user and developer community.
>
> = Community =
> There is

Re: [DISCUSS] DistributedLog Incubation Proposal

[Sijie Guo]

Thanks Eitan for adding me.

Sravya, cool! I am glad that you are interested in mentoring this project.
Shall I add you to the proposal?

Sijie

On Saturday, June 11, 2016, Eitan Adler <li...@eitanadler.com> wrote:

> + some people explicitly
>
> On 10 June 2016 at 12:42, Sravya Tirukkovalur <sra...@apache.org
> <javascript:;>> wrote:
> > Excited to see DistributedLog come to ASF!
> >
> > I see that you already have good list of nominated mentors. As a member
> of
> > recently graduated project, I can offer mentorship(informal) as well if
> > needed. I am not an IPMC member, so I guess I cannot be a formal mentor.
> >
> > Regards,
> >
> > On Wed, Jun 8, 2016 at 9:34 PM, Sijie Guo <si...@apache.org
> <javascript:;>> wrote:
> >
> >> Hi,
> >>
> >> I would like to propose DistributedLog to be an Apache Incubator
> project.
> >>
> >> DistributedLog is a high performance replicated log service.
> >> It offers durability, replication and strong consistency, which provides
> >> a fundamental building block for building reliable distributed systems,
> >> e.g replicated-state-machines, general pub/sub systems, distributed
> >> databases, distributed queues and etc.
> >>
> >> Here's a link to the proposal in the Incubator wiki
> >>
> >> https://wiki.apache.org/incubator/DistributedLogProposal
> >>
> >> I've also pasted the initial contents below.
> >>
> >> Thanks,
> >>
> >> Sijie
> >>
> >> = Abstract =
> >> DistributedLog is a high-performance replicated log service. It offers
> >> durability, replication and strong consistency, which provides a
> >> fundamental building block for building reliable distributed systems,
> >> e.g replicated-state-machines, general pub/sub systems, distributed
> >> databases, distributed queues and etc.
> >>
> >> See “Building Distributedlog - Twitter’s high performance replicated
> >> log service” for details:
> >>
> >>
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
> >>
> >> = Proposal =
> >> We propose to contribute DistributedLog codebase and associated
> >> artifacts (e.g. documentation, web-site content etc.) to the Apache
> >> Software Foundation with the intent of forming a productive,
> >> meritocratic and open community around DistributedLog’s continued
> >> development, according to the ‘Apache Way’.
> >>
> >> = Background =
> >> Engineers at Twitter began developing DistributedLog in early 2013.
> >> DistributedLog is described in a Twitter engineering blog post and
> >> presented at the Messaging Meetup in Sep 2015. It has been released as
> >> an Apache-licensed open-source project on GitHub in May 2016.
> >>
> >> DistributedLog is a high-performance replicated log service, which
> >> provides simple stream-oriented abstractions over log-segments and
> >> offers durability, replication and strong consistency for building
> >> reliable distributed systems. The features offered by DistributedLog
> >> includes:
> >>  * Simple high-level, stream oriented interface
> >>  * Naming and metadata scheme for managing streams and other entities
> >>  * Log data management policies, include data segmentation and data
> >> retention
> >>  * Fast write pipeline leveraging batching and compression
> >>  * Fast read mechanism leveraging long-poll and read-ahead caching
> >>  * Service tiers supporting writer fan-in and reader fan-out
> >>  * Geo-replicated logs
> >>
> >> DistributedLog’s most important benefit is high-performance with a
> >> strong durability guarantee, making it extremely appropriate for
> >> running different workloads from distributed database journaling to
> >> real-time stream computing. Its modern, layered architecture makes it
> >> easy to run the service tiers in multi-tenant datacenter environments
> >> such as Apache Mesos or cloud environments such as EC2.
> >>
> >> = Rationale =
> >> DistributedLog is designed to provide core fundamental features like
> >> high-performance, durability and strong consistency to anyone who is
> >> building reliable distributed systems, in a simple and efficient way.
> >>
> >> We believe that the ASF is the right venue to foster an open-source
> >> community around DistributedLog’s development. We expect that
> 

[DISCUSS] DistributedLog Incubation Proposal

[Sijie Guo]

 Committers =
 * Sijie Guo (Apache BookKeeper Committer, Twitter)
 * Robin Dhamankar (Apache BookKeeper Committer)
 * Leigh Stewart (Twitter)
 * Dave Rusek (Twitter)
 * Honggang Zhang (Twitter)
 * Jordan Bull (Twitter)
 * Satish Kotha (Twitter)
 * Aniruddha Laud
 * Franck Cuny (Twitter)
 * Eitan Adler (Twitter)

== Affiliations ==

Most of the initial committers are employees of Twitter, except Robin
Dhamankar and Aniruddha Laud.

= Sponsors =

== Champion ==

Flavio Junqueira

== Nominated Mentors ==

 * Flavio Junqueira
 * Chris Nauroth
 * Henry Saputra

= Sponsoring Entity =

We ask that the Apache Incubator PMC to sponsor this proposal.