Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc4
+1 binding [x] Download links are valid. [x] Checksums and signatures. gpg: Signature made Sat 27 Apr 2024 02:45:48 PM CST gpg:using RSA key 1E2CDAE4C08AD7D694D1CB139D7BE8E45E580BA4 gpg: Good signature from "chaokunyang (CODE SIGNING KEY) " [ultimate] apache-fury-0.5.0-incubating-src.tar.gz: OK [x] LICENSE/NOTICE files exist [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source on archlinux x86-64 Rust build passed: Finished `dev` profile [unoptimized + debuginfo] target(s) in 3.43s On Fri, May 3, 2024, at 11:49, Shawn Yang wrote: > +1 no-binding > > [x] Download Fury is valid. > [x] Checksums and PGP signatures are valid. > [x] Source code distributions have correct names matching the current > release. > [x] LICENSE and NOTICE files are correct. > [x] All files have license headers if necessary. > [x] No compiled archives bundled in source archive. > [x] Can compile from source. > > Best regards, > Chaokun Yang > > > On Tue, Apr 30, 2024 at 10:16 PM Shawn Yang wrote: > >> Hello everyone, >> >> This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc4. >> >> The Apache Fury community has voted and approved the release of Apache >> Fury(incubating) v0.5.0-rc4. We now kindly request the IPMC members >> review and vote for this release. >> >> Apache Fury(incubating) - A blazingly fast multi-language serialization >> framework powered by JIT and zero-copy. >> >> Fury community vote thread: >> https://lists.apache.org/thread/35slclopfngmz5ff47tt32m1fwjz1316 >> >> Vote result thread: >> https://lists.apache.org/thread/lnogbwfxw4hlkckl7nxpwwpy94zz6kv8 >> >> The release candidate: >> https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc4/ >> >> This release has been signed with a PGP available here: >> https://downloads.apache.org/incubator/fury/KEYS >> >> Git tag for the release: >> https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc4 >> >> Git commit for the release: >> >> https://github.com/apache/incubator-fury/commit/51beb134f517917d572dd0cf2b21534d74ecc726 >> >> Maven staging repo: >> https://repository.apache.org/content/repositories/orgapachefury-1006 >> >> How to Build and Test, please refer to: >> >> https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.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 >> >> To learn more about apache fury, please see https://fury.apache.org/ >> >> Checklist for reference: >> >> [ ] Download links are valid. >> [ ] Checksums and signatures. >> [ ] LICENSE/NOTICE files exist >> [ ] No unexpected binary files >> [ ] All source files have ASF headers >> [ ] Can compile from source >> >> >> Thanks, >> >> Chaokun Yang >> -- Xuanwo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc4
+1 no-binding [x] Download Fury is valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct. [x] All files have license headers if necessary. [x] No compiled archives bundled in source archive. [x] Can compile from source. Best regards, Chaokun Yang On Tue, Apr 30, 2024 at 10:16 PM Shawn Yang wrote: > Hello everyone, > > This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc4. > > The Apache Fury community has voted and approved the release of Apache > Fury(incubating) v0.5.0-rc4. We now kindly request the IPMC members > review and vote for this release. > > Apache Fury(incubating) - A blazingly fast multi-language serialization > framework powered by JIT and zero-copy. > > Fury community vote thread: > https://lists.apache.org/thread/35slclopfngmz5ff47tt32m1fwjz1316 > > Vote result thread: > https://lists.apache.org/thread/lnogbwfxw4hlkckl7nxpwwpy94zz6kv8 > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc4/ > > This release has been signed with a PGP available here: > https://downloads.apache.org/incubator/fury/KEYS > > Git tag for the release: > https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc4 > > Git commit for the release: > > https://github.com/apache/incubator-fury/commit/51beb134f517917d572dd0cf2b21534d74ecc726 > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachefury-1006 > > How to Build and Test, please refer to: > > https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.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 > > To learn more about apache fury, please see https://fury.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > > > Thanks, > > Chaokun Yang >
Re: License for text content
Thank you! Using Apache License 2.0 as the single license makes sense to me. Best, tison. Shane Curcuru 于2024年5月2日周四 19:55写道： > (Moving general@incubator and dev@community to BCC since this is really > a legal question about ASF licensing) > > tison wrote on 5/1/24 11:25 PM: > > Hi, > > > > IIUC, the Apache License 2.0 is mainly to license code and related stuff > > that constructs the final software. > > > > However, projects may also create text content like documents. Is it > > appropriate to use Apache License 2.0 for them (since quite a few terms > > may not be applicable)? Or what licenses shall we use? > > The ASF uses the Apache-2.0 license for our projects' own content that > is put into any releases, immaterial of type of content: > > https://apache.org/legal/src-headers.html#faq-docs > > Using a single license reduces complexity, and makes it simpler for > users to understand the issues around re-using ASF products. > > -- > - Shane >Member >The Apache Software Foundation > >
Re: License for text content
(Moving general@incubator and dev@community to BCC since this is really a legal question about ASF licensing) tison wrote on 5/1/24 11:25 PM: Hi, IIUC, the Apache License 2.0 is mainly to license code and related stuff that constructs the final software. However, projects may also create text content like documents. Is it appropriate to use Apache License 2.0 for them (since quite a few terms may not be applicable)? Or what licenses shall we use? The ASF uses the Apache-2.0 license for our projects' own content that is put into any releases, immaterial of type of content: https://apache.org/legal/src-headers.html#faq-docs Using a single license reduces complexity, and makes it simpler for users to understand the issues around re-using ASF products. -- - Shane Member The Apache Software Foundation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
