date:20200623

Re: [VOTE] Release Apache APISIX (Incubating) 1.4-RC1

2020-06-23 Thread Ming Wen

Welocme IPMC to vote, we got 0 +1 binding vote now.

Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing


YuanSheng Wang  于2020年6月24日周三 上午9:50写道：

> Carry my +1 non-binding from dev.
>
> I checked all those steps and run the Apache APISIX successfully at my
> local machine(fedora 31).
>
> And it shows the correct version `1.4`.
>
> [x] Download links are valid.
> [x] Checksums and PGP signatures are valid.
> [x] DISCLAIMER is included.
> [x] LICENSE and NOTICE files are good.
> [x] No binary file.
> [x] All files have license headers if necessary.
>
>
> On Tue, Jun 23, 2020 at 6:23 PM Nirojan Selvanathan 
> wrote:
>
> > Hello everyone,
> >
> > This is a call for the vote to release Apache APISIX (Incubating) version
> > 1.4-RC1.
> >
> > The Apache APISIX community has voted on and approved a proposal to
> > release Apache APISIX (Incubating) version 1.4-RC1.
> > We now kindly request the Incubator IPMC members review and vote on
> > this incubator release.
> >
> > Apache APISIX is a cloud-native microservices API gateway, delivering the
> > ultimate performance, security, open-source and scalable platform for all
> > your APIs and microservices.
> > Apache APISIX is based on Nginx and etcd, it has dynamic routing and
> > plug-in hot loading, which is especially suitable for API management
> under
> > the micro-service system.
> >
> > Apache APISIX community vote and result threads:
> >
> >
> https://lists.apache.org/thread.html/r3304413b3d69f8d388c9f42714616776d6148f7eb674794861edc790%40%3Cdev.apisix.apache.org%3E
> >
> > Release notes:
> > https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md#140
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-apisix/tree/v1.4
> >
> > Release Commit ID:
> >
> >
> https://github.com/apache/incubator-apisix/commit/f7584f680697179f5af44dbff5e26ad25cb860e8
> >
> > Keys to verify the Release Candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
> >
> > Steps to validating the release:
> >
> > 1. Download the release
> > ```
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz
> > ```
> >
> >
> > 2. Checksums and signatures
> > ```
> > wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
> > wget
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
> >
> > shasum -c apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
> > gpg --import KEYS
> >
> > # input `trust`, `5`, then `save`
> >
> > gpg --edit-key "Nirojan Selvanathan"
> > gpg --verify apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
> > apache-apisix-1.4-rc1-incubating-src.tar.gz
> > ```
> >
> > 3. Unzip and Check files
> > ```
> > tar zxvf apache-apisix-1.4-rc1-incubating-src.tar.gz
> > ```
> >
> > 4. This release contains the dashboard code for APISIX
> >
> >
> https://github.com/apache/incubator-apisix-dashboard/tree/329b092dcaa7a505dcdec86c667b6803f5863d94
> >
> >
> > 5. Build Apache APISIX:
> > https://github.com/apache/incubator-apisix/blob/v1.4/doc/how-to-build.md
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference:
> > [ ] Download links are valid.
> > [ ] Checksums and PGP signatures are valid.
> > [ ] DISCLAIMER is included.
> > [ ] LICENSE and NOTICE files are good.
> > [ ] No binary file.
> > [ ] All files have license headers if necessary.
> >
> > And below is a more detailed checklist:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > --
> > Best Regards,
> > S.Nirojan
> > Linked-in 
> >
>
>
> --
>
> *MembPhis*
> My GitHub: https://github.com/membphis
> Apache APISIX: https://github.com/apache/incubator-apisix
>

Re: [VOTE] Release Apache APISIX (Incubating) 1.4-RC1

2020-06-23 Thread YuanSheng Wang

Carry my +1 non-binding from dev.

I checked all those steps and run the Apache APISIX successfully at my
local machine(fedora 31).

And it shows the correct version `1.4`.

[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] DISCLAIMER is included.
[x] LICENSE and NOTICE files are good.
[x] No binary file.
[x] All files have license headers if necessary.


On Tue, Jun 23, 2020 at 6:23 PM Nirojan Selvanathan 
wrote:

> Hello everyone,
>
> This is a call for the vote to release Apache APISIX (Incubating) version
> 1.4-RC1.
>
> The Apache APISIX community has voted on and approved a proposal to
> release Apache APISIX (Incubating) version 1.4-RC1.
> We now kindly request the Incubator IPMC members review and vote on
> this incubator release.
>
> Apache APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security, open-source and scalable platform for all
> your APIs and microservices.
> Apache APISIX is based on Nginx and etcd, it has dynamic routing and
> plug-in hot loading, which is especially suitable for API management under
> the micro-service system.
>
> Apache APISIX community vote and result threads:
>
> https://lists.apache.org/thread.html/r3304413b3d69f8d388c9f42714616776d6148f7eb674794861edc790%40%3Cdev.apisix.apache.org%3E
>
> Release notes:
> https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md#140
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/
>
> Git tag for the release:
> https://github.com/apache/incubator-apisix/tree/v1.4
>
> Release Commit ID:
>
> https://github.com/apache/incubator-apisix/commit/f7584f680697179f5af44dbff5e26ad25cb860e8
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
>
> Steps to validating the release:
>
> 1. Download the release
> ```
> wget
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz
> ```
>
>
> 2. Checksums and signatures
> ```
> wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
> wget
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
> wget
>
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
>
> shasum -c apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
> gpg --import KEYS
>
> # input `trust`, `5`, then `save`
>
> gpg --edit-key "Nirojan Selvanathan"
> gpg --verify apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
> apache-apisix-1.4-rc1-incubating-src.tar.gz
> ```
>
> 3. Unzip and Check files
> ```
> tar zxvf apache-apisix-1.4-rc1-incubating-src.tar.gz
> ```
>
> 4. This release contains the dashboard code for APISIX
>
> https://github.com/apache/incubator-apisix-dashboard/tree/329b092dcaa7a505dcdec86c667b6803f5863d94
>
>
> 5. Build Apache APISIX:
> https://github.com/apache/incubator-apisix/blob/v1.4/doc/how-to-build.md
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] DISCLAIMER is included.
> [ ] LICENSE and NOTICE files are good.
> [ ] No binary file.
> [ ] All files have license headers if necessary.
>
> And below is a more detailed checklist:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> --
> Best Regards,
> S.Nirojan
> Linked-in 
>


-- 

*MembPhis*
My GitHub: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix

[VOTE] Release Apache IoTDB 0.10.0

2020-06-23 Thread Xiangdong Huang

Hello all,

This is a call for vote to release Apache IoTDB (Incubating) version
0.10.0, which is the 3rd major version (and the  8th minor version) of
Apache IoTDB Project.

The Apache IoTDB community has voted on and approved a proposal to release
Apache IoTDB (Incubating) version 0.10.0.

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Apache IoTDB (incubating) (Database for the Internet of Things) is an
integrated data management engine designed for timeseries data. It provides
users with services for data collection, storage and analysis.

IoTDB community vote and result thread:


Result (17 +1 votes from mentors, IPMCs, PPMCs, committers and other
contributors):

-
https://lists.apache.org/thread.html/rf40abefda97a0675cb44ae985e3a3b7741dcac90ac5b01408c6331f6%40%3Cdev.iotdb.apache.org%3E


Vote:

-
https://lists.apache.org/thread.html/r67d045df992a3d5d400dbe396e926ed847e4e102559c9c6508544009%40%3Cdev.iotdb.apache.org%3E

-
https://lists.apache.org/thread.html/r89794d3741f9f63757b09ec440fcd5d557346540d40e74c0dd27%40%3Cdev.iotdb.apache.org%3E

The release candidates (RC4):
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.0/rc4

Git tag for the release (RC4):
https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.0

Hash for the release tag:
f506d9c731231f97d8813528cbf062760d40

Release Notes:
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.0/rc4/RELEASE_NOTES.md

The artifacts have been signed with Key : 2206EF8F64C35889, which can be

found in the keys file:
https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS

Look at here for how to verify this release candidate:
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release

The vote will be open for at least 72 hours.

>From the PPMC Vote we carry over 3 binding IPMC Votes:

+1 from Justin Mclean,
+1 from Julian Feinauer,
+1 from Christofer Dutz

The vote will be passed if there is no -1 vote ( as there are 3 IPMC +1
votes already), but we still hope all other IPMCs vote for it.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Xiangdong Huang
Apache IoTDB (incubating)

Re: [VOTE] Apache Ratis Thirdparty Incubating Release 0.5.0 rc0

2020-06-23 Thread Xiaoyu Yao

+1

- Download Source and verify signatures and checksums
- Build successfully on Java 8.
  +hit one build issue with Java11(tracked by RATIS-986)
- Run all unit test

Thanks,
Xiaoyu

On Tue, Jun 23, 2020 at 1:23 PM Arpit Agarwal 
wrote:

> +1 (binding)
>
> - RC is in the right location
> - Incubating in name
> - Source matches git tag, no unexpected binaries
> - DISCLAIMER/LICENSE/NOTICE look ok
> - Verified signatures and checksums
> - Built from source
> - Successfully built Ratis using the generated thirdparty jars
>
>
> > On Jun 23, 2020, at 11:27 AM, Lokesh Jain  wrote:
> >
> > Hi Apache Ratis IPMC,
> >
> > Apache Ratis Thirdpardy 0.5.0-rc0 release is just passed on the PPMC
> vote. The vote thread can be found at
> >
> https://lists.apache.org/thread.html/re5bc083d795839c5a1267c7c65d4106b6059de22357e46601ce2f8fc%40%3Cdev.ratis.apache.org%3E
> <
> https://lists.apache.org/thread.html/re5bc083d795839c5a1267c7c65d4106b6059de22357e46601ce2f8fc@%3Cdev.ratis.apache.org%3E
> >
> >
> > Apache Ratis is an embeddable Raft implementation but this release
> artifact is only the packaging of some of the 3rd party dependencies.
> >
> > The git tag to be voted upon:
> >
> https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git=shortlog;a=tag;h=refs/tags/0.5.0-rc0
> <
> https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git=shortlog;a=tag;h=refs/tags/0.5.0-rc0
> >
> >
> > The git commit hash:
> >
> https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git;a=commit;h=c483b55186d10a99a37bbb8419c81a2ddcbe34bb
> <
> https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git;a=commit;h=c483b55186d10a99a37bbb8419c81a2ddcbe34bb
> >
> >
> > The source and binary tarballs can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.5.0/rc0/
> <
> https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.5.0/rc0/
> >
> > The fingerprint of key to sign release artifacts:
> > 33C4 1949 16C6 A4DD A6A6  A8BF C038 41BD 42EF CC9D
> >
> > Release artifacts are signed with one of the keys available at:
> > https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS <
> https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS>
> >
> > This vote will remain open for at least 72 hours. (2020-06-27 00:00 IST)
> >
> > Please vote on releasing this RC.  Thank you in advance.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Starting with my +1(non-binding).
> >
> > Regards,
> > Lokesh Jain
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

2020-06-23 Thread Justin Mclean

Hi,

> the consensus passed, so we should proceed according to the consensus.


It’s unclear to me what you think of as consensus here, can you care to specify 
what the project is going to do?

Justin



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

Re: [ANNOUNCE] Apache DataSketches C++ 2.0.0-incubating released!

2020-06-23 Thread Furkan KAMACI

Hi,

Congrats!

Kind Regards,
Furkan KAMACI

On Tue, Jun 23, 2020 at 11:24 PM leerho  wrote:

> Congratulations!   And thank you!  This was a major release effort!
>
> Lee.
>
> On Tue, Jun 23, 2020 at 12:06 PM Jon Malkin  wrote:
>
>> Hello All,
>>
>> 1. Apache DataSketches C++ 2.0.0-incubating has been released!
>>
>> NOTE 1: This is the core C++ component of the DataSketches library
>> that includes all the sketch algorithms in production-ready packages. This
>> package includes a header-only library and can also build a package for
>> use with Python 3.
>>
>> NOTE 2: This is a new major version using semantic versioning. There
>> are breaking API changes from the 1.x line. It also includes several bug
>> fixes.
>>
>> Vote Thread Permalink:
>>
>>
>> https://lists.apache.org/thread.html/rfdf8d99742a39f8c47583ed181e79f9973b1f15c5e4ab904b3cbd391%40%3Cgeneral.incubator.apache.org%3E
>> There were 3 binding (+1) votes: Justin Mclean, Furkan Kamaci, Evans
>> Ye
>>
>> 2. Source repository:
>> https://github.com/apache/incubator-datasketches-cpp
>>
>> Git Tag for this release: 90b6689
>> https://github.com/apache/incubator-datasketches-cpp/tree/2.0.x-incubating
>> on branch 2.0.X-incubating
>>
>> 3. Dist/release:
>> https://dist.apache.org/repos/dist/release/incubator/datasketches/cpp/2.0.0-incubating/
>>
>> 4. Build and test instructions:
>> C++ unit tests:
>>
>> https://github.com/apache/incubator-datasketches-cpp/tree/2.0.x-incubating/README.md
>> Python:
>> https://github.com/apache/incubator-datasketches-cpp/blob/2.0.x-incubating/python/README.md
>>
>> Thank you to the IPMC members and community for taking the time to review
>> and provide guidance on our release!
>>
>> On behalf of the Apache DataSketches Community,
>>
>> Jon Malkin
>> jmal...@apache.org
>>
>

Re: [ANNOUNCE] Apache DataSketches C++ 2.0.0-incubating released!

2020-06-23 Thread leerho

Congratulations!   And thank you!  This was a major release effort!

Lee.

On Tue, Jun 23, 2020 at 12:06 PM Jon Malkin  wrote:

> Hello All,
>
> 1. Apache DataSketches C++ 2.0.0-incubating has been released!
>
> NOTE 1: This is the core C++ component of the DataSketches library
> that includes all the sketch algorithms in production-ready packages. This
> package includes a header-only library and can also build a package for
> use with Python 3.
>
> NOTE 2: This is a new major version using semantic versioning. There
> are breaking API changes from the 1.x line. It also includes several bug
> fixes.
>
> Vote Thread Permalink:
>
>
> https://lists.apache.org/thread.html/rfdf8d99742a39f8c47583ed181e79f9973b1f15c5e4ab904b3cbd391%40%3Cgeneral.incubator.apache.org%3E
> There were 3 binding (+1) votes: Justin Mclean, Furkan Kamaci, Evans Ye
>
> 2. Source repository:
> https://github.com/apache/incubator-datasketches-cpp
>
> Git Tag for this release: 90b6689
> https://github.com/apache/incubator-datasketches-cpp/tree/2.0.x-incubating
> on branch 2.0.X-incubating
>
> 3. Dist/release:
> https://dist.apache.org/repos/dist/release/incubator/datasketches/cpp/2.0.0-incubating/
>
> 4. Build and test instructions:
> C++ unit tests:
>
> https://github.com/apache/incubator-datasketches-cpp/tree/2.0.x-incubating/README.md
> Python:
> https://github.com/apache/incubator-datasketches-cpp/blob/2.0.x-incubating/python/README.md
>
> Thank you to the IPMC members and community for taking the time to review
> and provide guidance on our release!
>
> On behalf of the Apache DataSketches Community,
>
> Jon Malkin
> jmal...@apache.org
>

Re: [VOTE] Apache Ratis Thirdparty Incubating Release 0.5.0 rc0

2020-06-23 Thread Arpit Agarwal

+1 (binding)

- RC is in the right location
- Incubating in name
- Source matches git tag, no unexpected binaries
- DISCLAIMER/LICENSE/NOTICE look ok
- Verified signatures and checksums
- Built from source
- Successfully built Ratis using the generated thirdparty jars


> On Jun 23, 2020, at 11:27 AM, Lokesh Jain  wrote:
> 
> Hi Apache Ratis IPMC,
> 
> Apache Ratis Thirdpardy 0.5.0-rc0 release is just passed on the PPMC vote. 
> The vote thread can be found at
> https://lists.apache.org/thread.html/re5bc083d795839c5a1267c7c65d4106b6059de22357e46601ce2f8fc%40%3Cdev.ratis.apache.org%3E
>  
> 
> 
> Apache Ratis is an embeddable Raft implementation but this release artifact 
> is only the packaging of some of the 3rd party dependencies.
> 
> The git tag to be voted upon:
> https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git=shortlog;a=tag;h=refs/tags/0.5.0-rc0
>  
> 
> 
> The git commit hash:
> https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git;a=commit;h=c483b55186d10a99a37bbb8419c81a2ddcbe34bb
>  
> 
> 
> The source and binary tarballs can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.5.0/rc0/ 
> 
> The fingerprint of key to sign release artifacts:
> 33C4 1949 16C6 A4DD A6A6  A8BF C038 41BD 42EF CC9D
> 
> Release artifacts are signed with one of the keys available at:
> https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS 
> 
> 
> This vote will remain open for at least 72 hours. (2020-06-27 00:00 IST)
> 
> Please vote on releasing this RC.  Thank you in advance.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> Starting with my +1(non-binding).
> 
> Regards,
> Lokesh Jain


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

[ANNOUNCE] Apache DataSketches C++ 2.0.0-incubating released!

2020-06-23 Thread Jon Malkin

Hello All,

1. Apache DataSketches C++ 2.0.0-incubating has been released!

NOTE 1: This is the core C++ component of the DataSketches library
that includes all the sketch algorithms in production-ready packages. This
package includes a header-only library and can also build a package for
use with Python 3.

NOTE 2: This is a new major version using semantic versioning. There
are breaking API changes from the 1.x line. It also includes several bug fixes.

Vote Thread Permalink:


https://lists.apache.org/thread.html/rfdf8d99742a39f8c47583ed181e79f9973b1f15c5e4ab904b3cbd391%40%3Cgeneral.incubator.apache.org%3E
There were 3 binding (+1) votes: Justin Mclean, Furkan Kamaci, Evans Ye

2. Source repository:
https://github.com/apache/incubator-datasketches-cpp

Git Tag for this release: 90b6689
https://github.com/apache/incubator-datasketches-cpp/tree/2.0.x-incubating
on branch 2.0.X-incubating

3. 
Dist/release:https://dist.apache.org/repos/dist/release/incubator/datasketches/cpp/2.0.0-incubating/

4. Build and test instructions:
C++ unit tests:
https://github.com/apache/incubator-datasketches-cpp/tree/2.0.x-incubating/README.md
Python: 
https://github.com/apache/incubator-datasketches-cpp/blob/2.0.x-incubating/python/README.md

Thank you to the IPMC members and community for taking the time to review
and provide guidance on our release!

On behalf of the Apache DataSketches Community,

Jon Malkin
jmal...@apache.org

[VOTE] Apache Ratis Thirdparty Incubating Release 0.5.0 rc0

2020-06-23 Thread Lokesh Jain

Hi Apache Ratis IPMC,

Apache Ratis Thirdpardy 0.5.0-rc0 release is just passed on the PPMC vote. The 
vote thread can be found at
https://lists.apache.org/thread.html/re5bc083d795839c5a1267c7c65d4106b6059de22357e46601ce2f8fc%40%3Cdev.ratis.apache.org%3E
 


Apache Ratis is an embeddable Raft implementation but this release artifact is 
only the packaging of some of the 3rd party dependencies.

The git tag to be voted upon:
https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git=shortlog;a=tag;h=refs/tags/0.5.0-rc0
 


The git commit hash:
https://gitbox.apache.org/repos/asf?p=incubator-ratis-thirdparty.git;a=commit;h=c483b55186d10a99a37bbb8419c81a2ddcbe34bb
 


The source and binary tarballs can be found at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/thirdparty/0.5.0/rc0/ 

The fingerprint of key to sign release artifacts:
33C4 1949 16C6 A4DD A6A6  A8BF C038 41BD 42EF CC9D

Release artifacts are signed with one of the keys available at:
https://dist.apache.org/repos/dist/dev/incubator/ratis/KEYS 


This vote will remain open for at least 72 hours. (2020-06-27 00:00 IST)

Please vote on releasing this RC.  Thank you in advance.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Starting with my +1(non-binding).

Regards,
Lokesh Jain

Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

2020-06-23 Thread Leonard Lausen

Hi Ciyong,

the consensus passed, so we should proceed according to the consensus.

Thank you
Leonard

On Tue, 2020-06-23 at 09:04 +, Chen, Ciyong wrote:
> Hi all,
> 
> I'm wondering if there's any further concerns for this "72 hours lazy
> consensus"?
> Shall we continue with the option of "I believe PPMC would prefer to put the
> ASF header on top of the file (ie. 2 headers)"
> 
> Thanks,
> -Ciyong
> 
> -Original Message-
> From: Leonard Lausen 
> Sent: Tuesday, June 16, 2020 7:06 AM
> To: d...@mxnet.incubator.apache.org; general@incubator.apache.org
> Subject: Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS]
> Re: [MENTORS] PPMC case-by-case decision for major modifications of third-
> party work guidance
> 
> Thank you everyone for your valuable advice.
> 
> > so if you did want to avoid including the license in your releases you
> > would either need to rely on the file as an external dependency or
> > completely reimplement the functionality not deriving it from this
> > file.
> 
> Including the BSD-3 style license in releases wouldn't be a problem, as it's
> compatible with Apache License 2. As there are substantial changes, I believe
> PPMC would prefer to put the ASF header on top of the file (ie. 2 headers) [72
> hours lazy consensus if there are no concerns]. We still need to declare all
> the numpy einsum derived files in the LICENSE and fix the inconsistency that
> ASF header was removed in src/operator/numpy/np_einsum_op-inl.h but remains in
> src/operator/numpy/np_einsum_path_op-inl.h
> 
> Related: As PPMC strives to provide partial API compatibility with NumPy in
> MXNet 2 based on the NumPy Array Function Protocol [1], could you clarify if
> these MXNet operators should be considered derived from NumPy (thus warranting
> the BSD-3 style license headers) solely based on integrating with the NumPy
> API and providing compatible operators? Or only (as in the einsum case above),
> if the actual implementation was derived from NumPy's implementation. I
> believe it's the latter, but please clarify if that's wrong.
> 
> Should ASF update the "Do not add the standard Apache License header to the
> top of third-party source files." at [2]? This sentence was the motivation to
> open this discussion thread, and according to the current consensus here is
> "incomplete". How about adding an "unless the third-party source file contains
> major modifications by ASF" to clarify?
> 
> Thank you
> Leonard
> 
> [1]: https://numpy.org/neps/nep-0018-array-function-protocol.html
> [2]: https://www.apache.org/legal/src-headers.html#3party
> 
> On Mon, 2020-06-15 at 09:36 -0400, John D. Ament wrote:
> > On Sat, Jun 13, 2020 at 2:19 PM Bob Paulin  wrote:
> > 
> > > Hi,
> > > 
> > > I agree there does not appear to be consensus on when it's
> > > appropriate to add Apache License Headers to Third Party code across
> > > projects.  Here is Justin's email that request the Apache Headers
> > > removed [1]
> > > 
> > > 
> > > 
> > > - file copyright  NumPy Developers [6] this file look to incorrectly
> > > have an ASF header on it 
> > > 6. ./src/operator/numpy/np_einsum_path_op-inl.h
> > > 
> > > 
> > > We want to make the choice that will be most sustainable for the
> > > project and most correct for the situation.
> > > 
> > > Based on the emails I linked in the prior email it does seem like
> > > the cases where dual headers are appropriate is when there are Major
> > > Modifications.  In the case of
> > > 
> > > np_einsum_path_op-inl.h
> > > 
> > > The file is derived from the implementation in Numpy [2].  If the
> > > implementation in Numpy changes will this file change?  If so then
> > > the community will be tasked with continuing to re-port the changes
> > > over that is always based on Numpy so it may be more appropriate to
> > > just keep the Numpy license.
> > > 
> > > Will MXNet likely evolve this file in a way that it's no longer
> > > resembles the Numpy implementation (Major Modification)?  If so it
> > > may be better to keep the Apache Header as going forward the file
> > > will represent the work of the MXNet community not that of Numpy.
> > > 
> > 
> > Keeping the (what appears to be) BSD-3 style license is perfectly fine
> > and is in fact what the NumPy license says to do.  We would only
> > change the license from the NumPy license to ALv2 if an SGA or ICLA is
> > received from all contributors historically on this file.  No matter
> > how drastic of modifications the MxNet community makes to it, it would
> > always be NumPy licensed; so if you did want to avoid including the
> > license in your releases you would either need to rely on the file as
> > an external dependency or completely reimplement the functionality not
> > deriving it from this file.  Whether or not the MxNet community
> > imports upstream changes or not is up to them, but either way you have a
> > derived work here.
> > 
> > John
> > 
> > 
> > > Hopefully the above helps clarify my

[VOTE] Release Apache APISIX (Incubating) 1.4-RC1

2020-06-23 Thread Nirojan Selvanathan

Hello everyone,

This is a call for the vote to release Apache APISIX (Incubating) version
1.4-RC1.

The Apache APISIX community has voted on and approved a proposal to
release Apache APISIX (Incubating) version 1.4-RC1.
We now kindly request the Incubator IPMC members review and vote on
this incubator release.

Apache APISIX is a cloud-native microservices API gateway, delivering the
ultimate performance, security, open-source and scalable platform for all
your APIs and microservices.
Apache APISIX is based on Nginx and etcd, it has dynamic routing and
plug-in hot loading, which is especially suitable for API management under
the micro-service system.

Apache APISIX community vote and result threads:
https://lists.apache.org/thread.html/r3304413b3d69f8d388c9f42714616776d6148f7eb674794861edc790%40%3Cdev.apisix.apache.org%3E

Release notes:
https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md#140

The release candidates:
https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/

Git tag for the release:
https://github.com/apache/incubator-apisix/tree/v1.4

Release Commit ID:
https://github.com/apache/incubator-apisix/commit/f7584f680697179f5af44dbff5e26ad25cb860e8

Keys to verify the Release Candidate:
https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS

Steps to validating the release:

1. Download the release
```
wget
https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz
```

2. Checksums and signatures
```
wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
wget
https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
wget
https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512

shasum -c apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
gpg --import KEYS

# input `trust`, `5`, then `save`

gpg --edit-key "Nirojan Selvanathan"
gpg --verify apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
apache-apisix-1.4-rc1-incubating-src.tar.gz
```

3. Unzip and Check files
```
tar zxvf apache-apisix-1.4-rc1-incubating-src.tar.gz
```

4. This release contains the dashboard code for APISIX
https://github.com/apache/incubator-apisix-dashboard/tree/329b092dcaa7a505dcdec86c667b6803f5863d94

5. Build Apache APISIX:
https://github.com/apache/incubator-apisix/blob/v1.4/doc/how-to-build.md

The vote will be open for at least 72 hours or until the necessary number
of votes is reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Checklist for reference:
[ ] Download links are valid.
[ ] Checksums and PGP signatures are valid.
[ ] DISCLAIMER is included.
[ ] LICENSE and NOTICE files are good.
[ ] No binary file.
[ ] All files have license headers if necessary.

And below is a more detailed checklist:
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

--
Best Regards,
S.Nirojan
Linked-in

RE: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

2020-06-23 Thread Chen, Ciyong

Hi all,

I'm wondering if there's any further concerns for this "72 hours lazy 
consensus"?
Shall we continue with the option of "I believe PPMC would prefer to put the 
ASF header on top of the file (ie. 2 headers)"

Thanks,
-Ciyong

-Original Message-
From: Leonard Lausen  
Sent: Tuesday, June 16, 2020 7:06 AM
To: d...@mxnet.incubator.apache.org; general@incubator.apache.org
Subject: Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: 
[MENTORS] PPMC case-by-case decision for major modifications of third-party 
work guidance

Thank you everyone for your valuable advice.

> so if you did want to avoid including the license in your releases you 
> would either need to rely on the file as an external dependency or 
> completely reimplement the functionality not deriving it from this 
> file.

Including the BSD-3 style license in releases wouldn't be a problem, as it's 
compatible with Apache License 2. As there are substantial changes, I believe 
PPMC would prefer to put the ASF header on top of the file (ie. 2 headers) [72 
hours lazy consensus if there are no concerns]. We still need to declare all 
the numpy einsum derived files in the LICENSE and fix the inconsistency that 
ASF header was removed in src/operator/numpy/np_einsum_op-inl.h but remains in 
src/operator/numpy/np_einsum_path_op-inl.h

Related: As PPMC strives to provide partial API compatibility with NumPy in 
MXNet 2 based on the NumPy Array Function Protocol [1], could you clarify if 
these MXNet operators should be considered derived from NumPy (thus warranting 
the BSD-3 style license headers) solely based on integrating with the NumPy API 
and providing compatible operators? Or only (as in the einsum case above), if 
the actual implementation was derived from NumPy's implementation. I believe 
it's the latter, but please clarify if that's wrong.

Should ASF update the "Do not add the standard Apache License header to the top 
of third-party source files." at [2]? This sentence was the motivation to open 
this discussion thread, and according to the current consensus here is 
"incomplete". How about adding an "unless the third-party source file contains 
major modifications by ASF" to clarify?

Thank you
Leonard

[1]: https://numpy.org/neps/nep-0018-array-function-protocol.html
[2]: https://www.apache.org/legal/src-headers.html#3party

On Mon, 2020-06-15 at 09:36 -0400, John D. Ament wrote:
> On Sat, Jun 13, 2020 at 2:19 PM Bob Paulin  wrote:
> 
> > Hi,
> > 
> > I agree there does not appear to be consensus on when it's 
> > appropriate to add Apache License Headers to Third Party code across 
> > projects.  Here is Justin's email that request the Apache Headers 
> > removed [1]
> > 
> > 
> > 
> > - file copyright  NumPy Developers [6] this file look to incorrectly 
> > have an ASF header on it 
> > 6. ./src/operator/numpy/np_einsum_path_op-inl.h
> > 
> > 
> > We want to make the choice that will be most sustainable for the 
> > project and most correct for the situation.
> > 
> > Based on the emails I linked in the prior email it does seem like 
> > the cases where dual headers are appropriate is when there are Major 
> > Modifications.  In the case of
> > 
> > np_einsum_path_op-inl.h
> > 
> > The file is derived from the implementation in Numpy [2].  If the 
> > implementation in Numpy changes will this file change?  If so then 
> > the community will be tasked with continuing to re-port the changes 
> > over that is always based on Numpy so it may be more appropriate to 
> > just keep the Numpy license.
> > 
> > Will MXNet likely evolve this file in a way that it's no longer 
> > resembles the Numpy implementation (Major Modification)?  If so it 
> > may be better to keep the Apache Header as going forward the file 
> > will represent the work of the MXNet community not that of Numpy.
> > 
> 
> Keeping the (what appears to be) BSD-3 style license is perfectly fine 
> and is in fact what the NumPy license says to do.  We would only 
> change the license from the NumPy license to ALv2 if an SGA or ICLA is 
> received from all contributors historically on this file.  No matter 
> how drastic of modifications the MxNet community makes to it, it would 
> always be NumPy licensed; so if you did want to avoid including the 
> license in your releases you would either need to rely on the file as 
> an external dependency or completely reimplement the functionality not 
> deriving it from this file.  Whether or not the MxNet community 
> imports upstream changes or not is up to them, but either way you have a 
> derived work here.
> 
> John
> 
> 
> > Hopefully the above helps clarify my perspective on how to determine 
> > case by case.  I don't see the dual license state as the simpler 
> > case in all situations.  I don't believe you would have to get the 
> > original committer to relicense the file to you in order to remove 
> > the additional license.  I believe the PPMC has all the authority it 
> > needs

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-23 Thread Justin Mclean (Jira)



[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142742#comment-17142742
 ] 

Justin Mclean commented on INCUBATOR-253:
-

The incubator has every right to ask podlings to comply with ASF policy. ASF 
policy is on top of what the Apache License allows.  The incubator also has the 
right to terminate a project if it doesn't comply with policy. See 
https://incubator.apache.org/policy/incubation.html#termination

Again I suggest you read https://issues.apache.org/jira/browse/LEGAL-515 


> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[VOTE] Release Apache DolphinScheduler (Incubating) 1.3.0 (ROUND2)

2020-06-23 Thread leon bao

Hello IPMC and DolphinScheduler Community,

This is a call for a vote to release Apache DolphinScheduler (Incubating)
version 1.3.0.

The Apache DolphinScheduler community has voted on and approved a proposal
to release
Apache DolphinScheduler (Incubating) version 1.3.0.

We now kindly request the Incubator IPMC members review and vote on this
incubator release.

Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow
scheduling system,
dedicated to solving the complex dependencies in data processing, making
the scheduling system out of the box for data processing.

DolphinScheduler community vote and result threads:
https://lists.apache.org/thread.html/r857ec990603ec2a4487db5ce9de0614e757a51e6235fd584953bc8c6%40%3Cdev.dolphinscheduler.apache.org%3E

https://lists.apache.org/thread.html/ra6db3fd9a263850e15741a03e21395477a3e14f8b9728e6b9dc3b1cd%40%3Cdev.dolphinscheduler.apache.org%3E

Release notes:
https://github.com/apache/incubator-dolphinscheduler/releases/tag/1.3.0

The release candidates:
https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/1.3.0/

Maven 2 staging repository:
https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1026/org/apache/dolphinscheduler/

Git tag for the release:
https://github.com/apache/incubator-dolphinscheduler/tree/1.3.0

Release Commit ID:
https://github.com/apache/incubator-dolphinscheduler/commit/05b6c54aeb88b19041cb27d94a5eb6c1c673d314

Keys to verify the Release Candidate:
https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS

Look at here for how to verify this release candidate:
https://dolphinscheduler.apache.org/en-us/docs/development/release.html

The vote will be open for at least 72 hours or until a necessary number of
votes are reached.
Please vote accordingly:

[ ] +1 approveg

[ ] +0 no opinion

[ ] -1 disapprove with the reason

Checklist for reference:

[ ] Download links are valid.

[ ] Checksums and PGP signatures are valid.

[ ] Source code artifacts have correct names matching the current release.

[ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.

[ ] All files have license headers if necessary.

[ ] No compiled archives bundled in source archive.

More detail checklist  please refer:
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist


The following votes are carried over from DolphinScheduler dev mailing list:
 +1  Furkan KAMACI
 +1  Kevin Ratnasekera

-- 
DolphinScheduler(Incubator)  PPMC
BaoLiang 鲍亮
leon...@apache.org

Re: [VOTE] Release Apache APISIX (Incubating) 1.4-RC1

Re: [VOTE] Release Apache APISIX (Incubating) 1.4-RC1

[VOTE] Release Apache IoTDB 0.10.0

Re: [VOTE] Apache Ratis Thirdparty Incubating Release 0.5.0 rc0

Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

Re: [ANNOUNCE] Apache DataSketches C++ 2.0.0-incubating released!

Re: [ANNOUNCE] Apache DataSketches C++ 2.0.0-incubating released!

Re: [VOTE] Apache Ratis Thirdparty Incubating Release 0.5.0 rc0

[ANNOUNCE] Apache DataSketches C++ 2.0.0-incubating released!

[VOTE] Apache Ratis Thirdparty Incubating Release 0.5.0 rc0

Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

[VOTE] Release Apache APISIX (Incubating) 1.4-RC1

RE: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

[VOTE] Release Apache DolphinScheduler (Incubating) 1.3.0 (ROUND2)

15 matches

Site Navigation

Mail list logo

Footer information