Re: [VOTE] Release Apache ECharts (incubating) 4.3.0 (release candidate 2)
+1 binding Checked - asc signed - sha512 checked - LICENSE and NOTICE there - DISCLAIMER there One question, when I run > shasum -c apache-echarts-4.3.0-rc.2-incubating-src.zip.sha512 Got > shasum: apache-echarts-4.3.0-rc.2-incubating-src.zip.sha512: no properly formatted SHA1 checksum lines found I manually compared the sha512, they are matched. How do you generate the sha512 file? And how do you check with command. Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108 Dave Fisher 于2019年9月12日周四 下午1:48写道： > +1 from me. > > I checked: > - Incubating in name > - DISCLAIMER exists > - LICENSE and NOTICE are fine > - No unexpected binary files > - Checked signature and checksum > > We should discuss the build instructions compared to test build > instructions on the dev@echarts mailing list. > > Regards, > Dave > > > On Sep 12, 2019, at 6:42 AM, Dave Fisher wrote: > > > > Inline > > > > Sent from my iPhone > > > >> On Sep 12, 2019, at 3:18 AM, SHUANG SU wrote: > >> > >> Justin & Furkan, thank you for the detailed check! > >> > >> There is a relevant build instruction in > >> > https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts > >> and the link is listed in `README.md`. > >> > >> But I also think it is not clear enough and the doc is on the > perspective > >> of echarts user but not echarts contributor. > >> > >> I will add instruction of "how to build from the source code" to > >> `README.md` directly, > >> and add the entry of `npm run build` and `npm run build:watch` to > >> `package.json`. > >> Hope that makes it better. > >> > >> Because it is an enhancement, could we include this modification of > >> `README.md` > >> in the future release, but not in this release? > > > > Yes. Please make the change for the future while we continue this VOTE > thread! > > > > Regards, > > Dave > >> > >> > >> Thanks, > >> -- > >> Su Shuang (100pah) > >> -- > >> > >> > >> > >>> On Thu, 12 Sep 2019 at 17:25, Furkan KAMACI > wrote: > >>> > >>> Hi, > >>> > >>> +1 from me. > >>> > >>> I checked: > >>> - Incubating in name > >>> - DISCLAIMER exists > >>> - LICENSE and NOTICE are fine > >>> - No unexpected binary files > >>> - Checked PGP signatures > >>> - Code compiles and tests successfully run > >>> > >>> I agree with Justin, build instructions should be more clear. On the > other > >>> hand, I'm not sure about the sha512 checksum file format. > >>> > >>> Kind Regards, > >>> Furkan KAMACI > >>> > >>> On Thu, Sep 12, 2019 at 6:01 AM Justin Mclean < > jus...@classsoftware.com> > >>> wrote: > >>> > Hi, > > +1 binding > > I checked: > - incubating in a name > - signature sand hashes correct > - DISCLAIMER exists > - LICENS and NOTICE file > - Now unexpected binary files in the release > - All source files have ASF headers > - Compiled from source release > > It would be good to see some build instruction in the source release. > There’s a build directory but it unclear what need to be done to build > >>> it. > I figured it out but it's not exactly obvious what is needed to be > done. > > 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 > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache ECharts (incubating) 4.3.0 (release candidate 2)
+1 from me. I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - Checked signature and checksum We should discuss the build instructions compared to test build instructions on the dev@echarts mailing list. Regards, Dave > On Sep 12, 2019, at 6:42 AM, Dave Fisher wrote: > > Inline > > Sent from my iPhone > >> On Sep 12, 2019, at 3:18 AM, SHUANG SU wrote: >> >> Justin & Furkan, thank you for the detailed check! >> >> There is a relevant build instruction in >> https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts >> and the link is listed in `README.md`. >> >> But I also think it is not clear enough and the doc is on the perspective >> of echarts user but not echarts contributor. >> >> I will add instruction of "how to build from the source code" to >> `README.md` directly, >> and add the entry of `npm run build` and `npm run build:watch` to >> `package.json`. >> Hope that makes it better. >> >> Because it is an enhancement, could we include this modification of >> `README.md` >> in the future release, but not in this release? > > Yes. Please make the change for the future while we continue this VOTE thread! > > Regards, > Dave >> >> >> Thanks, >> -- >> Su Shuang (100pah) >> -- >> >> >> >>> On Thu, 12 Sep 2019 at 17:25, Furkan KAMACI wrote: >>> >>> Hi, >>> >>> +1 from me. >>> >>> I checked: >>> - Incubating in name >>> - DISCLAIMER exists >>> - LICENSE and NOTICE are fine >>> - No unexpected binary files >>> - Checked PGP signatures >>> - Code compiles and tests successfully run >>> >>> I agree with Justin, build instructions should be more clear. On the other >>> hand, I'm not sure about the sha512 checksum file format. >>> >>> Kind Regards, >>> Furkan KAMACI >>> >>> On Thu, Sep 12, 2019 at 6:01 AM Justin Mclean >>> wrote: >>> Hi, +1 binding I checked: - incubating in a name - signature sand hashes correct - DISCLAIMER exists - LICENS and NOTICE file - Now unexpected binary files in the release - All source files have ASF headers - Compiled from source release It would be good to see some build instruction in the source release. There’s a build directory but it unclear what need to be done to build >>> it. I figured it out but it's not exactly obvious what is needed to be done. 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ECharts (incubating) 4.3.0 (release candidate 2)
Inline Sent from my iPhone > On Sep 12, 2019, at 3:18 AM, SHUANG SU wrote: > > Justin & Furkan, thank you for the detailed check! > > There is a relevant build instruction in > https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts > and the link is listed in `README.md`. > > But I also think it is not clear enough and the doc is on the perspective > of echarts user but not echarts contributor. > > I will add instruction of "how to build from the source code" to > `README.md` directly, > and add the entry of `npm run build` and `npm run build:watch` to > `package.json`. > Hope that makes it better. > > Because it is an enhancement, could we include this modification of > `README.md` > in the future release, but not in this release? Yes. Please make the change for the future while we continue this VOTE thread! Regards, Dave > > > Thanks, > -- > Su Shuang (100pah) > -- > > > >> On Thu, 12 Sep 2019 at 17:25, Furkan KAMACI wrote: >> >> Hi, >> >> +1 from me. >> >> I checked: >> - Incubating in name >> - DISCLAIMER exists >> - LICENSE and NOTICE are fine >> - No unexpected binary files >> - Checked PGP signatures >> - Code compiles and tests successfully run >> >> I agree with Justin, build instructions should be more clear. On the other >> hand, I'm not sure about the sha512 checksum file format. >> >> Kind Regards, >> Furkan KAMACI >> >> On Thu, Sep 12, 2019 at 6:01 AM Justin Mclean >> wrote: >> >>> Hi, >>> >>> +1 binding >>> >>> I checked: >>> - incubating in a name >>> - signature sand hashes correct >>> - DISCLAIMER exists >>> - LICENS and NOTICE file >>> - Now unexpected binary files in the release >>> - All source files have ASF headers >>> - Compiled from source release >>> >>> It would be good to see some build instruction in the source release. >>> There’s a build directory but it unclear what need to be done to build >> it. >>> I figured it out but it's not exactly obvious what is needed to be done. >>> >>> 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
Re: [VOTE] Recommend Apache Rya graduation to Top Level Project resolution to the Board
+1 Great work! Thanks Sharan On Fri, 6 Sep 2019, 18:29 Adina Crainiceanu, wrote: > The Apache Rya (incubating) community is bringing the attached resolution > to graduate to a Top Level Project up for a formal IPMC VOTE. > > -We completed all the tasks documented in the status file [1] > -The name Apache Rya was approved by the Brand Management Committee [2] > -We had four Apache releases with three different release managers > -Our community grew during incubation and we learned to function following > the Apache Way > -We discussed on the dev@ list about our readiness for graduation [3], we > voted [4], and the result of the vote was positive [5] > -We went through the process of assessing our project against the Apache > Maturity model [6] and we believe we are ready to graduate and continue to > grow as a Top Level Project. > -We worked on creating a graduation resolution and we selected a Chair [7]. > > Please take a minute to vote on whether or not the IPMC should recommend > the resolution below to the Board by responding with one of the following: > > [ ] +1 Apache Rya should graduate > [ ] 0 No opinion > [ ] -1 Apache Rya should not graduate because... > > The VOTE is open for a minimum of 72 hours. > > Thank you, > Adina, on behalf of Apache Rya (incubating) community > > [1] https://incubator.apache.org/projects/rya.html > [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-135 > [3] > > https://lists.apache.org/thread.html/dd09c2060a754e69e093404e0d57239a555ab5e7d702cf76fd02f820@%3Cdev.rya.apache.org%3E > [4] > > https://lists.apache.org/thread.html/10f04a55e0f6d4c09d3ffeac487b0bf309eb8e5058f950778214faeb@%3Cdev.rya.apache.org%3E > [5] > > https://lists.apache.org/thread.html/d1664b17d8a6bf3d3e4e5f28382bc360fe974f1db8f880c6d97ff278@%3Cdev.rya.apache.org%3E > [6] > > https://cwiki.apache.org/confluence/display/RYA/Apache+Maturity+Evaluation+for+Rya > [7] > > https://lists.apache.org/thread.html/3007163bc654df45109c38b4d9a53c7b2137ad0fef660429938a282b@%3Cprivate.rya.apache.org%3E > > _ > Proposed graduation resolution: > > Establish the Apache Rya 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 scalable storage, retrieval, and analysis of RDF data. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Rya Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Rya Project be and hereby is responsible for > the creation and maintenance of software related to scalable storage, > retrieval, and analysis of RDF data; and be it further > > RESOLVED, that the office of "Vice President, Apache Rya" 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 Rya Project, and to > have primary responsibility for management of the projects within the > scope of responsibility of the Apache Rya 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 Rya Project: > > * Aaron Mihalik > * Adina Crainiceanu > * Billie Rinaldi > * Caleb Meier > * David Lotts > * David Rapp > * Jennifer Brown > * Josh Elser > * Puja Valiyil > * Roshan Punnoose > * Steve R Wagner > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Adina Crainiceanu be > appointed to the office of Vice President, Apache Rya, 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 Rya Project be and hereby is tasked with the > migration and rationalization of the Apache Incubator Rya podling; and > be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > Rya podling encumbered upon the Apache Incubator PMC are hereafter > discharged. >
Re: [VOTE] Release Apache ECharts (incubating) 4.3.0 (release candidate 2)
Justin & Furkan, thank you for the detailed check! There is a relevant build instruction in https://echarts.apache.org/en/tutorial.html#Create%20Custom%20Build%20of%20ECharts and the link is listed in `README.md`. But I also think it is not clear enough and the doc is on the perspective of echarts user but not echarts contributor. I will add instruction of "how to build from the source code" to `README.md` directly, and add the entry of `npm run build` and `npm run build:watch` to `package.json`. Hope that makes it better. Because it is an enhancement, could we include this modification of `README.md` in the future release, but not in this release? Thanks, -- Su Shuang (100pah) -- On Thu, 12 Sep 2019 at 17:25, Furkan KAMACI wrote: > Hi, > > +1 from me. > > I checked: > - Incubating in name > - DISCLAIMER exists > - LICENSE and NOTICE are fine > - No unexpected binary files > - Checked PGP signatures > - Code compiles and tests successfully run > > I agree with Justin, build instructions should be more clear. On the other > hand, I'm not sure about the sha512 checksum file format. > > Kind Regards, > Furkan KAMACI > > On Thu, Sep 12, 2019 at 6:01 AM Justin Mclean > wrote: > > > Hi, > > > > +1 binding > > > > I checked: > > - incubating in a name > > - signature sand hashes correct > > - DISCLAIMER exists > > - LICENS and NOTICE file > > - Now unexpected binary files in the release > > - All source files have ASF headers > > - Compiled from source release > > > > It would be good to see some build instruction in the source release. > > There’s a build directory but it unclear what need to be done to build > it. > > I figured it out but it's not exactly obvious what is needed to be done. > > > > Thanks, > > Justin > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Release Apache DataSketches-cpp (incubating) 1.0.0 [RC2]
Hi, +1 from me! (binding - carrying my vote) Kind Regards, Furkan KAMACI On Mon, Sep 9, 2019 at 10:05 PM Alexander Saydakov < sayda...@verizonmedia.com> wrote: > Dear IPMC and Community, > > This is a call for vote to release Apache DataSketches-cpp version > 1.0.0-incubating > > This is a C++ version of the DataSketches core library with Python > bindings. > > This is the first release of this component. > > We are not going to release any artifacts besides the source code. > > Results from the PPMC vote: > 3 votes were cast. All of the votes were (+1). One of the votes was from a > mentor. > > http://mail-archives.apache.org/mod_mbox/datasketches-dev/201909.mbox/thread > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/datasketches/cpp/1.0.0-incubating-rc2/ > > Source repository: > https://github.com/apache/incubator-datasketches-cpp > > Git tag for this release: > > https://github.com/apache/incubator-datasketches-cpp/releases/tag/1.0.0-incubating-rc2 > > The artifact has been signed with key: > pub 4096R/A8E8B4E0 2019-08-20 Alexander Saydakov (CODE SIGNING KEY) < > al...@apache.org> > Fingerprint=40A2 47F6 1E8C 6C75 678C 69C5 6848 6114 A8E8 B4E0 > > The public signing key can be found in the KEYS file: > https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS > > Changes from the RC1: > - added license to make files > - building and running unit tests does not require pybind11 (dependency for > Python bindings) > - better build instructions > > This library was intended to be header-only, but this goal was not fully > achieved yet with CPC sketch code. This work is in progress. > > Building and running unit tests requires CppUnit. > > Installing CppUnit on OSX: brew install cppunit > Installing CppUnit on RHEL: yum install cppunit-devel > > There are currently two ways of building: using existing make files and > generating make files using cmake. Exsisting make files might not work on > all platforms or with all C++ compilers. Generating make files using cmake > should solve this problem, but it currently requires cmake version 3.12.0 > or higher that might not be readily available as a package on all > platforms. > > Installing the latest cmake on OSX: brew install cmake > > Building and running unit tests using existing make files: > $ make > $ make test > > Building and running unit tests using cmake: > $ mkdir build > $ cd build > $ cmake .. > $ make > $ make test > > Building Python bindings requires cmake 3.12 or higher and pybind11. > Please see the following document for details: > > https://github.com/apache/incubator-datasketches-cpp/blob/1.0.0-incubating-rc2/python/README.md > > This is the second stage vote. The vote will remain open for at least 72 > hours and at least 3 (+1) IPMC votes or a majority of (+1) are acquired. > > Please vote accordingly: > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > Alexander Saydakov > al...@apache.org >
Re: [VOTE] Release Apache ECharts (incubating) 4.3.0 (release candidate 2)
Hi, +1 from me. I checked: - Incubating in name - DISCLAIMER exists - LICENSE and NOTICE are fine - No unexpected binary files - Checked PGP signatures - Code compiles and tests successfully run I agree with Justin, build instructions should be more clear. On the other hand, I'm not sure about the sha512 checksum file format. Kind Regards, Furkan KAMACI On Thu, Sep 12, 2019 at 6:01 AM Justin Mclean wrote: > Hi, > > +1 binding > > I checked: > - incubating in a name > - signature sand hashes correct > - DISCLAIMER exists > - LICENS and NOTICE file > - Now unexpected binary files in the release > - All source files have ASF headers > - Compiled from source release > > It would be good to see some build instruction in the source release. > There’s a build directory but it unclear what need to be done to build it. > I figured it out but it's not exactly obvious what is needed to be done. > > Thanks, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
FW: [ANNOUNCE] Apache Milagro (incubating) Crypto C & JS Libraries 1.0.0 release
Hi, This email to annou...@apache.org just got approved, so I thought I'd forward it here in case anyone's not subscribed to that list. Many thanks to everyone again. Regards, John -Original Message- From: John McCane-Whitney Sent: 09 September 2019 19:02 To: annou...@apache.org Subject: [ANNOUNCE] Apache Milagro (incubating) Crypto C & JS Libraries 1.0.0 release Hi, On behalf of the Apache Milagro (incubating) community, I'd like to announce our first ASF releases: Apache Milagro Crypto C 1.0.0-incubating milagro-crypto-c is a modern cryptographic C library that focuses on Elliptic Curve Cryptography but has support for legacy systems that require RSA. There is support for three different security levels; 128, 192 and 256 bit. It has been written only in C and has no external dependencies other than an entropy source. Measures have been taken in the code base to prevent side channel attacks. Pairing based cryptography (PBC) is a maturing field that has recently gained widespread acceptance. The library supports schemes that make use of PBC such as BLS for short signatures and MPIN for multi-factor authentication (MFA). Release notes: https://github.com/apache/incubator-milagro-crypto-c/releases/tag/1.0.0 Documentation: http://milagro.apache.org/cdocs/index.html Apache Milagro Crypto JS 1.0.0-incubating milagro-crypto-js is the JavaScript equivalent of milagro-crypto-c. It has all the same functionality, API and even the intermediate calculated values in the functions are the same. This library allows you to run software only MFA (multi-factor authentication) using M-PIN in the browser which, to the best of our knowledge, is the only such implementation of software only MFA (multi-factor authentication) in this context. Release notes: https://github.com/apache/incubator-milagro-crypto-js/releases/tag/1.0.0 Documentation: http://milagro.apache.org/docs/amcl-javascript-api/ Source distributions for both can be found here: http://milagro.apache.org/docs/downloads/ Please refer to each repo's README for build and test instructions. Vote result thread: https://lists.apache.org/thread.html/8631d1d67fc2c846f68ef7cdb2e2914e870cdfaaa943e78c0349f458@%3Cgeneral.incubator.apache.org%3E Many thanks to all our contributors and mentors and to the IPMC for their input and guidance. John McCane-Whitney Director of Product Qredo Ltd. Apache Milagro (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. 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. smime.p7s Description: S/MIME cryptographic signature
