Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc2
This release process spans the 2024 New Year's Day, I have raised a PR[1] this morning to update the NOTICE year. It will be included in the next release if it’s not a blocking issue. [1] https://github.com/apache/incubator-celeborn/pull/2198 Thanks, Cheng Pan > On Jan 2, 2024, at 15:37, Kent Yao wrote: > > +1 (binding), I have checked: > > [✓] The checksums and signatures are validated > [ ] The LICENSE is fine, but NOTICE files[1-6] need to be updated to 2024(I'm > not sure whether this is a blocker not but better to be fixed). > [✓] DISCLAIMER is present > [✓] No binary files found in the source release > [✓] Incubating in the name > [✓] Built from source > > Kent Yao > > [1] ./NOTICE > [2] ./client-spark/spark-3-shaded/src/main/resources/META-INF/NOTICE > [3] ./client-spark/spark-2-shaded/src/main/resources/META-INF/NOTICE > [4] ./client-flink/flink-1.14-shaded/src/main/resources/META-INF/NOTICE > [5] ./client-flink/flink-1.15-shaded/src/main/resources/META-INF/NOTICE > [6] ./client-flink/flink-1.17-shaded/src/main/resources/META-INF/NOTICE > > > On 2024/01/02 03:11:27 Nicholas Jiang wrote: >> Hi IPMC, >> >> This is a call for a vote to release Apache Celeborn (Incubating) >> 0.3.2-incubating-rc2 >> >> The Apache Celeborn community has voted on and approved a proposal to >> release Apache Celeborn (Incubating) version 0.3.2-incubating-rc2. >> We now kindly request the Incubator PMC members review and vote on this >> incubator release. >> >> celeborn@dev vote thread: >> >> https://lists.apache.org/thread/zq5kb3ovr53xkocgh0jyx30nsrjqw9do >> >> celeborn@dev vote result thread: >> >> https://lists.apache.org/thread/d5djbkc4tdn1t06bpr9wbgryswvp2fm8 >> >> The git tag to be voted upon: >> >> https://github.com/apache/incubator-celeborn/releases/tag/v0.3.2-incubating-rc2 >> >> The git commit hash: >> 0dccad38e28554c36a5eef98de2540d996f946f7 >> >> The source and binary artifacts can be found at: >> >> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.2-incubating-rc2 >> >> The staging repo: >> >> https://repository.apache.org/content/repositories/orgapacheceleborn-1048 >> >> Fingerprint of the PGP key release artifacts are signed with: >> D73CADC1DAB63BD3C770BB6D9476842D24B7C885 >> >> My public key to verify signatures can be found in: >> >> https://dist.apache.org/repos/dist/release/incubator/celeborn/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 (and the reason) >> >> Checklist for release: >> >> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist >> >> Steps to validate the release: >> >> https://www.apache.org/info/verification.html >> >> Instructions for making binary artifacts from source: >> build/make-distribution.sh --release >> >> Regards, >> Nicholas Jiang > > - > 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 Celeborn(Incubating) 0.3.2-incubating-rc2
+1 (binding), I have checked: [✓] The checksums and signatures are validated [ ] The LICENSE is fine, but NOTICE files[1-6] need to be updated to 2024(I'm not sure whether this is a blocker not but better to be fixed). [✓] DISCLAIMER is present [✓] No binary files found in the source release [✓] Incubating in the name [✓] Built from source Kent Yao [1] ./NOTICE [2] ./client-spark/spark-3-shaded/src/main/resources/META-INF/NOTICE [3] ./client-spark/spark-2-shaded/src/main/resources/META-INF/NOTICE [4] ./client-flink/flink-1.14-shaded/src/main/resources/META-INF/NOTICE [5] ./client-flink/flink-1.15-shaded/src/main/resources/META-INF/NOTICE [6] ./client-flink/flink-1.17-shaded/src/main/resources/META-INF/NOTICE On 2024/01/02 03:11:27 Nicholas Jiang wrote: > Hi IPMC, > > This is a call for a vote to release Apache Celeborn (Incubating) > 0.3.2-incubating-rc2 > > The Apache Celeborn community has voted on and approved a proposal to > release Apache Celeborn (Incubating) version 0.3.2-incubating-rc2. > We now kindly request the Incubator PMC members review and vote on this > incubator release. > > celeborn@dev vote thread: > > https://lists.apache.org/thread/zq5kb3ovr53xkocgh0jyx30nsrjqw9do > > celeborn@dev vote result thread: > > https://lists.apache.org/thread/d5djbkc4tdn1t06bpr9wbgryswvp2fm8 > > The git tag to be voted upon: > > https://github.com/apache/incubator-celeborn/releases/tag/v0.3.2-incubating-rc2 > > The git commit hash: > 0dccad38e28554c36a5eef98de2540d996f946f7 > > The source and binary artifacts can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.2-incubating-rc2 > > The staging repo: > > https://repository.apache.org/content/repositories/orgapacheceleborn-1048 > > Fingerprint of the PGP key release artifacts are signed with: > D73CADC1DAB63BD3C770BB6D9476842D24B7C885 > > My public key to verify signatures can be found in: > > https://dist.apache.org/repos/dist/release/incubator/celeborn/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 (and the reason) > > Checklist for release: > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > Steps to validate the release: > > https://www.apache.org/info/verification.html > > Instructions for making binary artifacts from source: > build/make-distribution.sh --release > > Regards, > Nicholas Jiang - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [LICENSE QUESTION] Use jmh as a benchmark tool
FYI this is how Fury excludes benchmark from the distribution[1] Best, tison. [1] https://github.com/apache/incubator-fury/pull/1272 John D. Ament 于2023年12月31日周日 23:44写道： > > On Fri, Dec 29, 2023 at 7:50 PM Julian Hyde wrote: > > > According to https://issues.apache.org/jira/browse/LEGAL-450, it's OK > > to use a GPL linter. And a project can use GPL "build tools provided > > they leave no code traces (licensed under a cat X license) in your > > final release artifacts". > > > > This is the section that I was raising a concern around. In Fury's > benchmark module, there are traces of JMH present in the resulting source > code, e.g. you need JMH to compile the test code. Yes, it can be excluded > if that's the right thing to do. And if there's enough evidence say that > is the right course of action that's fine (though it seems a little odd to > me that the git repo doesn't match the source release to me). > > > > > > In Calcite we use jmh on the understanding that it does not produce > > any artifacts and therefore was acceptable. > > > > Can someone explain how a benchmarking utility is different from a linter? > > > > Julian > > > > On Wed, Dec 27, 2023 at 9:19 AM tison wrote: > > > > > > > For instance, if your maven build is `-Pbenchmark` and it's clear > > > > that the user needs to include this license when compiling from source. > > > > > > Yeah. I'm going to collaborate with Fury to follow this approach and > > > document clearly how a developer can intentionally run benchmark with > > > JMH as a dep. > > > > > > Best, > > > tison. > > > > > > John D. Ament 于2023年12月28日周四 01:07写道： > > > > > > > > On Wed, Dec 27, 2023 at 11:38 AM tison wrote: > > > > > > > > > > application, a developer has preinstalled the JDK (or using a > > manager of > > > > > > some kind to install it - so not something we're forcing upon > > them). In > > > > > > > > > > No. To running a Java Application in a normal way, the JRE is > > > > > required. Saying "not something we're forcing upon them" sounds > > > > > sophistry. > > > > > > > > > > Best, > > > > > tison. > > > > > > > > > > tison 于2023年12月28日周四 00:27写道： > > > > > > > > > > > > Hi John, > > > > > > > > > > > > Glad to hear your feedback. Reply inline: > > > > > > > > > > > > > In the case of JMH, the repository I linked above forces the > > user to > > > > > download > > > > > > > the additional dependency from maven central (or similar > > repository) > > > > > rather > > > > > > > than relying on the system preinstalled library. > > > > > > > > > > > > From a technical view, this is not true because you can download > > the > > > > > > libs manually and place them under MAVEN_HOME. Then it can be > > regarded > > > > > > as a "system preinstalled library". It's the same as download JDK > > and > > > > > > place them under JAVA_HOME. > > > > > > > > > > > > > Except that's not how these libraries are listed within your pom > > file. If > > > > there was a step where you required a developer to download these > > files, > > > > what you're describing would be accurate, but they're downloaded in an > > > > automated fashion. Keep in mind, this isn't the JMH that's distributed > > > > with the JDK that you're using here, it's an add-on library you're > > using. > > > > > > > > > > > > > > > > > > > > > you can't use org.openjdk.jmh:* as a compile/test compile > > > > > > > dependency in your project > > > > > > > > > > > > fury-benchmark is not released in binary form. But we can of course > > > > > > make it an optional dependency (or the entire module optionally) > > > > > > behind a profile and deactivated by default so that it's the same > > as > > > > > > how ASF projects can optionally depend on MySQL Connector Java > > under > > > > > > the same license. > > > > > > > > > > > > > The question here isn't about binary form. Keep in mind that first and > > > > foremost ASF projects produce source code releases, the convenience > > > > binaries are a separate artifact. I'm presently approaching your > > thread > > > > focused on the source code release. I can see your point though and > > that's > > > > where I'm suggesting asking legal may give you additional guidance > > that I > > > > could see leading to a similar situation as Java 9 JavaScript > > embeddings. > > > > Just keep in mind that you're making a module optional to compile, > > rather > > > > than optional to use, even though it's only being used for testing > > purposes > > > > and our expectation (even though it may differ from reality) is that > > we're > > > > reviewing the contents of the source bundle that a user downloads to > > > > compile your code, not the binary artifact they depend upon in their > > > > projects. > > > > > > > > > > > > > > > > > > > > A related discussion can be found at [1]. > > > > > > > > > > > > > Yes, and Hen's response is very appropriate to that situation. It's > > not > > > > really relevant to your situation though since the concern in this >
RE: [VOTE] Release Apache Answer(Incubating) v1.2.1-RC1 (Round2)
+1 non-binding I have checked out-dated KEYS have been removed, and the README.md file has been adjusted to recommend that users run the newest published version.
[CANCEL][VOTE] Release Apache DevLake (Incubating) v0.19.0-rc3
Hello everyone, I'm canceling this vote https://lists.apache.org/thread/ymth9hgp6p82pclcbtght4cpdvyvz5mf I will further optimize the license and start a new vote process. Thanks a lot for all your help. Best, Zikuan An
Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc3
Hello everyone, I'm canceling this vote https://lists.apache.org/thread/ymth9hgp6p82pclcbtght4cpdvyvz5mf I will further optimize the license and start a new vote process. Thanks a lot for all your help. Best, Zikuan An
[VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc2
Hi IPMC, This is a call for a vote to release Apache Celeborn (Incubating) 0.3.2-incubating-rc2 The Apache Celeborn community has voted on and approved a proposal to release Apache Celeborn (Incubating) version 0.3.2-incubating-rc2. We now kindly request the Incubator PMC members review and vote on this incubator release. celeborn@dev vote thread: https://lists.apache.org/thread/zq5kb3ovr53xkocgh0jyx30nsrjqw9do celeborn@dev vote result thread: https://lists.apache.org/thread/d5djbkc4tdn1t06bpr9wbgryswvp2fm8 The git tag to be voted upon: https://github.com/apache/incubator-celeborn/releases/tag/v0.3.2-incubating-rc2 The git commit hash: 0dccad38e28554c36a5eef98de2540d996f946f7 The source and binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.2-incubating-rc2 The staging repo: https://repository.apache.org/content/repositories/orgapacheceleborn-1048 Fingerprint of the PGP key release artifacts are signed with: D73CADC1DAB63BD3C770BB6D9476842D24B7C885 My public key to verify signatures can be found in: https://dist.apache.org/repos/dist/release/incubator/celeborn/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 (and the reason) Checklist for release: https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist Steps to validate the release: https://www.apache.org/info/verification.html Instructions for making binary artifacts from source: build/make-distribution.sh --release Regards, Nicholas Jiang
Re: Incubator Information Terrakube
Hello Xuanwo. Let me explain with an example using terraform. The Terraform CLI can help you to write your IaC, but sometimes you need more than just the CLI, you need to get Terraform Enterprise/Cloud to handle your infrastructure using different organization, teams, policies, handle a private registry to manage modules or providers, execute terraform remotely, have a UI to check your infrastructure and other features. In the same way Terrakube could be the enterprise backend that you can use with Opentofu to handle your infrastructure at enterprise level the same way like proprietary tools like like the following products: - Terraform Enterprise/Cloud - https://spacelift.io/ - https://www.scalr.com/ - https://www.env0.com/ We did some videos in the past, those are a little bit outdated but maybe they can help you to understand and have a better idea. https://youtu.be/LvJXFgkM9Zo?si=ShUdL2MatKuT4FOG https://youtu.be/QUz82AeB0mc?si=Eg7ZVrMpj2FtyPXN I hope this information can help you, let me know if you have more questions I will be happy to answer Regards. El sáb, 30 de dic de 2023, 20:16, Xuanwo escribió: > Wow, interesting project! > > I have a question unrelated to the Apache Incubator: What is the > difference > between this project and https://opentofu.org/? > > On Sat, Dec 30, 2023, at 04:10, alfredo españa wrote: > > Hello > > > > We have been working on an open source project called Terrakube that is > an > > open source alternative to proprietary tools like Terraform Enterprise or > > Terraform Cloud. In the last couple of months we have noticed an > increasing > > interest in a project like this that help to manage infrascture > > > > Project Links: > > - https://terrakube.org/ > > - https://docs.terrakube.io/ > > - https://github.com/AzBuilder/terrakube > > > > We would like to see if this project is a good candidate to be in the > > apache incubator program > > > > Regards. > > -- > Xuanwo >
