Re: [VOTE] Release Apache OpenDAL(incubating) v0.39.0-rc2 - Incubator Vote Round 1

+1 (binding) I checked = LICENSE / NOTICE / DISCLAIMER file exist = License headers are properly set = No unexpected binaries files = Can compile from source with rustc 1.71.1 (eb26296b5 2023-08-03) on macOS M1 chip Best, tison. Xuanwo 于2023年8月6日周日 00:08写道： > Carry my non-binding VOTE f

Re: [VOTE] Release Apache OpenDAL(incubating) v0.39.0-rc2 - Incubator Vote Round 1

ranch for the release: > > https://github.com/apache/incubator-opendal/tree/release-0.39.0-rc2 > > Please download, verify, and test. > > The VOTE will pass after got 3 binding approve. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > >

[VOTE] Release Apache OpenDAL(incubating) v0.39.0-rc2 - Incubator Vote Round 1

binding approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about apache opendal, please see https://opendal.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected

Re: [RESULT][VOTE] Release Apache OpenDAL(incubating) 0.38.1 - Incubator Vote Round 1

wrote: > > Hi Incubator PMC, > > > > The vote to release Apache OpenDAL(incubating) 0.38.1 has passed with > > 3 + 1 binding and 0 non-binding votes, no +0 or -1 votes. > > > > Binding votes： > > > > - CalvinKirs > > > > - tison >

Re: [RESULT][VOTE] Release Apache OpenDAL(incubating) 0.38.1 - Incubator Vote Round 1

My vote is not binding (since I'm not incubator committers) On Fri, Jul 21, 2023, at 12:31, cai lue wrote: > Hi Incubator PMC, > > The vote to release Apache OpenDAL(incubating) 0.38.1 has passed with > 3 + 1 binding and 0 non-binding votes, no +0 or -1 votes. > > Binding

[RESULT][VOTE] Release Apache OpenDAL(incubating) 0.38.1 - Incubator Vote Round 1

Hi Incubator PMC, The vote to release Apache OpenDAL(incubating) 0.38.1 has passed with 3 + 1 binding and 0 non-binding votes, no +0 or -1 votes. Binding votes： - CalvinKirs - tison - Xuanwo - Justin Vote thread: https://lists.apache.org/thread/jokj2v9p7zwozjpz1hjpd5k2jbgzo5oh Thanks

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.1-rc1 - Incubator Vote Round 1

+1 （binding） I checked: - incubating in name - signatures and hashes are fine - disclaimer exists - license and notice files look good - file have correct ASF headers if necessary On Thu, Jul 20, 2023 at 6:39 PM tison wrote: > > +1 (binding) > > I checked: > - incubating in name

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.1-rc1 - Incubator Vote Round 1

+1 (binding) I checked: - incubating in name - signatures and checksum are file - No unexpected binary files - LICENSE and NOTICE are fine - DISCLAIMER file exists - Compiled from source Best, tison. Xuanwo 于2023年7月18日周二 13:20写道： > Thanks for the VOTE and verify! > > > 1. ./bin

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.1-rc1 - Incubator Vote Round 1

Thanks for the VOTE and verify! > 1. ./bindings/python/python/opendal/layers.pyi Tracked at https://github.com/apache/incubator-opendal/issues/2662, we expect to fix it in next release. > 2. ./examples/rust/01-init-operator/src/main.rs Those files are served as rust examples docs, we p

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.1-rc1 - Incubator Vote Round 1

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are file - No unexpected binary files - LICENSE and NOTICE are fine - a few files don’t have ASF headers e.g. [1][2] I don’t have an environment set up to compile this, but including some easy to find instructions in the

[VOTE] Release Apache OpenDAL(incubating) 0.38.1-rc1 - Incubator Vote Round 1

binding approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about apache opendal, please see https://opendal.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary

[Result][VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

Hi Incubator PMC, The vote to release Apache OpenDAL(incubating) 0.38.0-rc1 has passed with 3 +1 binding and 2 +1 non-binding votes, no +0 or -1 votes. Binding votes： - PJ Fanning - tison - Willem Jiang Non-Binding votes: - Xuanwo - Kent Yao Vote thread: https://lists.apache.org/thread

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

+1 (nonbinding), I have checked: [✓] The checksums and signatures are validated [✓] The LICENSE and NOTICE are fine [✓] DISCLAIMER is present [✓] No binary files in the source release [✓] incubating in the name [✓] Successfully built the binary from the source on my Mac Kent Yao On 2023/07/04

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

+1. Here is what I checked: - The checksums and signatures are validated. - The LICENSE and NOTICE files look good to me. - There is a DISCLAIMER file about incubating. - No binary files in the source release. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Jun 28, 2023 at 10:31 PM

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

+1 binding I checked - GPG sign matched - Checksum verified - LICENSE and NOTICE exist - DISCLIAIMER exists - Compile from source Best, tison. Xuanwo 于2023年7月3日周一 00:18写道： > Carry my non-binding vote from the OpenDAL Community: > > - [x] Download links are valid. > - [x] C

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

x] LICENSE/NOTICE files exist - [x] No unexpected binary files - [x] All source files have ASF headers - [x] Can compile from source (tested on Archlinux x86_64) On Thu, Jun 29, 2023, at 01:48, PJ Fanning wrote: > Thanks Xuanwo for the explanation. > > +1 (binding) > > - I chec

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

Thanks Xuanwo for the explanation. +1 (binding) - I checked the downloads and the SHA512 and ASC files are valid. - LICENSE/NOTICE/DISCLAIMER are fine - no binary files - ASF headers on source files - `cargo build` works fine On Wed, 28 Jun 2023 at 17:43, Xuanwo wrote: > > Thanks for r

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

r contains any code from bb8-memcached. The comment here is outdated and needs to be updated. On Wed, Jun 28, 2023, at 23:08, PJ Fanning wrote: > The release looks good to me, generally. > > I'm wondering about your LICENSE [1] though. > It doesn't appear to acknowledge some t

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

The release looks good to me, generally. I'm wondering about your LICENSE [1] though. It doesn't appear to acknowledge some third party code that is borrowed [2] [3]. Apologies if this has been addressed before but I can't find any discussion about this in previous vote thread

[VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

binding approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about apache opendal, please see https://opendal.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary

[RESULT][VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

Hi Incubator PMC, The vote to release Apache OpenDAL(incubating) 0.37.0-rc1 has passed with 4 +1 binding votes, no +0 or -1 votes. Binding votes： - tison - Sheng Wu - Willem Jiang - Liu Ted Vote thread: https://lists.apache.org/thread/05g171bk4k08krhvrs46v6hym7lrnc4j Thanks for reviewing and

回复：Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

+1 (Binding) I checked and all good to go. Ted Liu 2023 年 6 月 16 日周五 16:38，Willem Jiang 写道： +1. Here is what I checked: - The checksums and signatures are validated. - The LICENSE and NOTICE files look good to me. - There is a DISCLAIMER file about incubating. - No binary files in the

Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

+1. Here is what I checked: - The checksums and signatures are validated. - The LICENSE and NOTICE files look good to me. - There is a DISCLAIMER file about incubating. - No binary files in the source release. I checked the build file of other bindings, we need to add build instructions for

[VOTE] Release Apache Teaclave (incubating) v0.6.0-rc.1

Hello Incubator PMC, I am pleased to be calling this vote for the release of Apache Teaclave (incubating) 0.6.0 (release candidate 1). The Apache Teaclave (incubating) community has voted and approved the release. The voting thread is https://lists.apache.org/thread

Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

21:46, Sheng Wu wrote: > Checked > 1. Compiling `cargo build` from source codes > 2. Version correct > 3. License and Notice exist for source codes. > 4. No License and Notice for binary. So far, I skip the check only due > to DISCLAIMER exists. This should be verified before the gradu

Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

Checked 1. Compiling `cargo build` from source codes 2. Version correct 3. License and Notice exist for source codes. 4. No License and Notice for binary. So far, I skip the check only due to DISCLAIMER exists. This should be verified before the graduation preparation. Before the vote, I want to

Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

+1 (binding) I checked - [x] Download links are valid. [x] Checksums and signatures. [x] + incubating in artifacts name [x] LICENSE/NOTICE files exist + DISCLAIMER exists [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source - with `cargo build' T

[VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

binding approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason To learn more about apache opendal, please see https://opendal.apache.org/ Checklist for reference: [ ] Download links are valid. [ ] Checksums and signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary

[RESULT][VOTE] Release Apache OpenDAL (incubating) v0.36.0-rc.1 (Round 2)

Hello everyone, Thanks for your review and vote for "Release Apache OpenDAL (Incubating) v0.36.0-rc.1" I'm happy to announce the vote has passed: 3 binding votes and 3 non-binding votes, no +0 or -1 votes. Thanks for reviewing and voting. +3 (binding) +1, from: - tison - Xiaoq

[RESULT][VOTE] Release Apache OpenDAL (incubating) v0.34.0-rc1, v0.35.0-rc1, v0.36.0-rc1 (Round 1)

.36.0-rc1 (Round 1)： The vote shares the same title with the vote in dev@o.a.o, resulting in it being missing from the Gmail client. Xuanwo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional comman

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, > I opened an issue in https://github.com/dermesser/leveldb-rs/issues/26. > The auther confirmed the original and gave some explanation about the > different license. In general if something is ported to anther language it keeps the same license. It this case both licenses are compatible wi

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

find out what should be added > to LICENSE (and NOTICE) or if there are any other issues. I can see there > further 3rd party software included in your source please than needs to bee > mentioned in LICENSE. > > Re [1] it is under the MIT license but that may not accurate

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, I would need to do a review in more detail to find out what should be added to LICENSE (and NOTICE) or if there are any other issues. I can see there further 3rd party software included in your source please than needs to bee mentioned in LICENSE. Re [1] it is under the MIT license but

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

ce/sgx_backtrace_sys/libbacktrace/config.sub > > There are also a number of file copyright the Free Software Foundation. (also > in libbacktrace) > > I’ve not looked at each one and the first couple do seem to be false > positives. However this file [1], which might incor

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

HI, Based on this it seems “Apache 2.0 with LLVM exception” is OK, it’s just nt been added to the category A list yet. [1] Kind Regards, Justin 1.https://issues.apache.org/jira/browse/LEGAL-494

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

/libbacktrace/config.sub There are also a number of file copyright the Free Software Foundation. (also in libbacktrace) I’ve not looked at each one and the first couple do seem to be false positives. However this file [1], which might incorrectly has a ASF header on it, seems to be a 1:1

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi Justin, Thanks for your comments. Could you please point out which GPL licensed software is included in the release? We have already removed GPL licensed software that we think is GPL. Thanks, He On Mon, May 15, 2023 at 1:04 PM Justin Mclean wrote: > Hi, > > A quick glance at thi

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi, A quick glance at this release shows it still includes GPL licensed software. Anything with that's GPL licensed can't be included in a ASF software release or be a non optional dependancy. What licensing issues were corrected in this release from the previous one? Kind Regards, Justin P.S

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi, I would also remove it from GitHub as it is still been advertised as a release to the wider public there. Kind Regards, Justin > On 15 May 2023, at 12:20 pm, He Sun wrote: > > Hi Justin, > > The v0.5.0-rc.1 is my first release. I misunderstood that 72 hour voting, so &

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi Justin, The v0.5.0-rc.1 is my first release. I misunderstood that 72 hour voting, so I finished the voting and merged those release commits in github before receiving your comments. To make the release number consistent with the commits in github, I fixed the problems you pointed out in a

[VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.1

Hi all, I am pleased to be calling this vote for the release of Apache Teaclave (incubating) 0.5.1 (release candidate 1). The Apache Teaclave (incubating) community has voted and approved the release. The result thread is https://lists.apache.org/thread/knnbbjg8h5y4j3tnochjcz48dbtmmqvs The

Incubator-SVN-Clutch-Analysis-part-1 build job

FYI, I just cancelled the following Incubator-SVN-Clutch-Analysis-part-1 build run: https://ci-builds.apache.org/job/Incubator/job/Incubator-SVN-Clutch-Analysis-part-1/1599/ It had been running for 2 days and 10 hours, where normally it should take only a couple of minutes. Not sure why it got

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi, Please remove the 0.5.0 download from this page https://teaclave.apache.org/download/ . You cannot put unreleased software on your download page. Justin

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi Justin, Thanks for your attention. I am working on your suggestions and will get back to you then. Any suggestion is welcome and we hope you continue to advise teaclave. Best, He On 2023/04/11 07:40:44 Justin Mclean wrote: > Hi, > > I‘ll also note that the code contains code under the GPL

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi, I‘ll also note that the code contains code under the GPL license, and you are not abiding by the arms of the license or informing your users of this. GPL code is considered category X and cannot be included in a source release. This issue and the compiled code issues were pointed out severa

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

HI, -1 (binding) due to compiled code in the source release. I checked: - incubating in name - signature and hashes are fine - WIP disclaimer exists - LICENSE needs work - Unexpected binary files in release. This includes multiple .wasm and .exe files. - ASF header on ASF files but hard to

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

one that participated. The vote to release Apache > > Teaclave (incubating) version 0.5.0 Release Candidate 1 is now closed. > > > > The vote PASSED with 4 binding +1, 0 non binding +1 and 0 -1 votes: > > > > Binding votes: > > - Gordon King > > - Ran D

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi, Voting is not over, only IPMC voting is binding. On 2023/04/03 02:28:05 He Sun wrote: > Thanks to everyone that participated. The vote to release Apache > Teaclave (incubating) version 0.5.0 Release Candidate 1 is now closed. > > The vote PASSED with 4 binding +1, 0 non binding

[RESULT][VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Thanks to everyone that participated. The vote to release Apache Teaclave (incubating) version 0.5.0 Release Candidate 1 is now closed. Vote thread: https://lists.apache.org/thread/6xbzdbrcd35drh7315mcsp8ko49mlx23 The vote PASSED with 4 binding +1, 0 non binding +1 and 0 -1 votes: Binding votes

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi Gang, I will update the year before next relase. Thank you for voting. Sincerely, He On 2023/04/02 05:19:45 li gang wrote: > +1 (binding) > I checked > - Files have the word incubating in their name. > - Checksums and signatures are valid. > - DISCLAIMER-WIP,LICENSE and NOT

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Thanks to everyone that participated. The vote to release Apache Teaclave (incubating) version 0.5.0 Release Candidate 1 is now closed. The vote PASSED with 4 binding +1, 0 non binding +1 and 0 -1 votes: Binding votes: - Gordon King - Ran Duan - Pei Wang - Gang Li I will release Apache Teaclave

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

+1 (binding) I checked - Files have the word incubating in their name. - Checksums and signatures are valid. - DISCLAIMER-WIP,LICENSE and NOTICE files exist. - No Unexpected Binary Files. - Need to update the NOTICE year next release. He Sun 于2023年3月30日周四 11:32写道： > Hi all, > > I am p

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

+1 On 2023/03/31 05:02:00 Duan Ran wrote: > + 1 > > On 2023/03/30 03:32:23 He Sun wrote: > > Hi all, > > > > I am pleased to be calling this vote for the fifth release of > > Apache Teaclave (incubating) 0.5.0 (release candidate 1). > > The Apache Teacla

Re: [VOTE] Release Apache Paimon (incubating) paimon-shade 1.0, release candidate #1

Thank you very much, Yu! Apache Paimon (incubating) paimon-shade 1.0 RC1 is canceled. Best, Jingsong On Fri, Mar 31, 2023 at 4:21 PM Yu Li wrote: > > FWIW, please also refer to the incubator policy [1] and podling constraints > [2] for incubator release management. > > Bes

Re: [VOTE] Release Apache Paimon (incubating) paimon-shade 1.0, release candidate #1

FWIW, please also refer to the incubator policy [1] and podling constraints [2] for incubator release management. Best Regards, Yu [1] https://incubator.apache.org/policy/incubation.html#releases [2] https://incubator.apache.org/guides/releasemanagement.html#podling_constraints On Fri, 31 Mar

Re: [VOTE] Release Apache Paimon (incubating) paimon-shade 1.0, release candidate #1

-1 (binding) Problems found: - Release files don't have the word "incubating" in their names - No DISCLAIMER file found - The NOTICE years of the META-INFO/NOTICE file nested in the generated shading jars are not correct ("Copyright 2023-2023" expected but "Copyrigh

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

+ 1 On 2023/03/30 03:32:23 He Sun wrote: > Hi all, > > I am pleased to be calling this vote for the fifth release of > Apache Teaclave (incubating) 0.5.0 (release candidate 1). > The Apache Teaclave (incubating) community has voted and approved the > release, with five +1

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

+1 (binding) Thanks. On Wed, Mar 29, 2023 at 8:33 PM He Sun wrote: > Hi all, > > I am pleased to be calling this vote for the fifth release of > Apache Teaclave (incubating) 0.5.0 (release candidate 1). > The Apache Teaclave (incubating) community has voted and approved the >

[VOTE] Release Apache Paimon (incubating) paimon-shade 1.0, release candidate #1

Hello Incubator Community, This is a call for a vote to release Apache Paimon (Incubating) paimon-shade version 1.0 (release candidate 1) Vote thread: https://lists.apache.org/thread/fmt340yhjwvxgnh4zzpfqzypwl1ykbld Result thread: https://lists.apache.org/thread/5q790myc0xtlyxgyjblfq266fj3jxlfy

[VOTE] Release Apache Teaclave (incubating) v0.5.0-rc.1

Hi all, I am pleased to be calling this vote for the fifth release of Apache Teaclave (incubating) 0.5.0 (release candidate 1). The Apache Teaclave (incubating) community has voted and approved the release, with five +1 votes.  Vote thread: https://lists.apache.org/thread

Re: +1 (non-binding) Linkis is a valuable project，good luck.

sorry for the wrong reply > 在 2022年12月1日，15:00，guosp <15764973...@163.com> 写道： > >  >

Re: +1 (non-binding)

sorry for the wrong reply. > 在 2022年12月1日，15:28，郭书培 <15764973...@163.com> 写道： > >  > Linkis is a valuable project, good luck. > > > - > To unsubscribe, e-mail: general-unsubscr...@incubat

+1 (non-binding)

Linkis is a valuable project, good luck. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

+1 (non-binding) Linkis is a valuable project，good luck.

[RESULT][VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi all, The vote to release Apache Teaclave (incubating) version 0.4.0 Release Candidate 1 in general@incuabator is now closed. Vote thread: https://lists.apache.org/thread/0gz5gwybgk5vfvgnxzxrhkgbhk88fpwd The vote PASSED with 3 binding +1, 1 non binding +1 and 0 -1 votes: Binding votes

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi all, Thanks to everyone that participated. The vote to release Apache Teaclave (incubating) version 0.4.0 Release Candidate 1 in general@incuabator is now closed. Vote thread: https://lists.apache.org/thread/0gz5gwybgk5vfvgnxzxrhkgbhk88fpwd The vote PASSED with 3 binding +1, 1 non binding +1

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Thanks Matt. We have another release for Teaclave TrustZone SDK v0.2.0-rc.2 also in the voting process. Please help to review and vote for it. Thanks. Mingshen [1] [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2: https://lists.apache.org/thread

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

+1 Note that the NOTICE file has a slightly outdated copyright year now and should be updated. — Matt Sicker > On Mar 26, 2022, at 17:08, Mingshen Sun wrote: > > Hi all, > > I am pleased to be calling this vote for the third release of > Apache Teaclave (incubating) 0.4.0

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi Craig and incubator community, I did try to reach out to our other mentors in the private@teaclave mailing list. No response yet. I hope other IPMC can help with our two recent releases [1, 2]. In the meantime, I'll start another thread to call for more mentors in case our existings ar

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi Craig, Thanks! Gordon and Furkan have voted for the release. Let me check with others. Mingshen On Tue, Apr 12, 2022 at 1:46 PM Craig Russell wrote: > > Hi, > > You have six Mentors. Have you asked them to review and vote? > > Warm regards, > Craig > > >

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

; > Mingshen > > On Tue, Apr 5, 2022 at 4:10 PM Mingshen Sun wrote: >> >> Thanks! >> >> We still need one more IPMC vote for the final release. >> >> >> Mingshen >> >> On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI wrote: >>&

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

> On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI wrote: > > > > Hi, > > > > +1 (binding) > > > > Kind Regards, > > Furkan KAMACI > > > > On 4 Apr 2022 Mon at 23:29 Mingshen Sun wrote: > > > > > Hi all, > > > > > &

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Thanks! We still need one more IPMC vote for the final release. Mingshen On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI wrote: > > Hi, > > +1 (binding) > > Kind Regards, > Furkan KAMACI > > On 4 Apr 2022 Mon at 23:29 Mingshen Sun wrote: > > > Hi all, > &g

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi, +1 (binding) Kind Regards, Furkan KAMACI On 4 Apr 2022 Mon at 23:29 Mingshen Sun wrote: > Hi all, > > We still need TWO more IPMC binding votes for this release [1]. Please > let me know if there's anything I can help with. Thanks. > > Mingshen > > [1] https:

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi all, We still need TWO more IPMC binding votes for this release [1]. Please let me know if there's anything I can help with. Thanks. Mingshen [1] https://incubator.apache.org/policy/incubation.html#releases On Thu, Mar 31, 2022 at 6:56 PM Gordon wrote: > > LGTM, +1 (bindi

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

LGTM, +1 (binding), Thanks On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun wrote: > Hi all, > > We need more votes from IPMC for this release. Please kindly help to > review this new release. Thanks! > > Mingshen > > On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen wr

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi all, We need more votes from IPMC for this release. Please kindly help to review this new release. Thanks! Mingshen On Wed, Mar 30, 2022 at 6:13 PM Zhaofeng Chen wrote: > > +1 (binding) > > I checked > - Include the word incubating in the release filename > - LICENSE and

Re: [VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

+1 (binding) I checked - Include the word incubating in the release filename - LICENSE and NOTICE files exist - DISCLAIMER file exist - Build successfully by following the instruction Best, Zhaofeng On Sat, Mar 26, 2022 at 3:09 PM Mingshen Sun wrote: > Hi all, > > I am pleased to b

[VOTE] Release Apache Teaclave (incubating) v0.4.0-rc.1

Hi all, I am pleased to be calling this vote for the third release of Apache Teaclave (incubating) 0.4.0 (release candidate 1). The Apache Teaclave (incubating) community has voted and approved the release, with six +1 votes from IPMC members (Hongbo Chen, Yulong Zhang, Ran Duan, Yu Ding

Re: clutch analysis part 1 failing: status pages not updating

>> which can be reused in a good way. It’s just that there will be additional >> work. >> >> I doubt I’ll have time to address this before the weekend. >> >> Regards, >> Dave >> >>> On Jan 4, 2022, at 1:36 PM, Wilfred Spiegelenburg

Re: Looking for a champion: resurrect log4j 1.x

ven if it is used would be > difficult. However, there is nothing stopping people who are interested > forking log4j 1.x and working on it elsewhere. Has that option been > considered? > > Kind Regards, > Justin > ---

Re: Looking for a champion: resurrect log4j 1.x

it is used would be difficult. However, there is nothing stopping people who are interested forking log4j 1.x and working on it elsewhere. Has that option been considered? Kind Regards, Justin - To unsubscribe, e-mail: general

Re: Looking for a champion: resurrect log4j 1.x

simply taking the last log4j 1 release, removing JMSAppender.class from the JAR, and publishing them to our Nexus or whatever with a modified version. This is what regulators and compliance officers will care about. It is being done as a stopgap and I can’t say if it would be acceptable or not as a

Re: Looking for a champion: resurrect log4j 1.x

t; There is a reason we are stuck on Log4J 1. I wish you could just hear this, > acknowledge it, and service the concerns of users in this regard without > the dictatorial attitude by continuing to release version 1 with security > fixes applied. That's all I think interested parties

Re: Looking for a champion: resurrect log4j 1.x

t;> in defiance of the community of users that have made the points I have >> just >>> written here abundantly clear for years. >> >> The Logging PMC is the owner of Log4j 1.x. We declared it EOL in 2015. Not >> one single complaint was received nor were any proposa

Re: Looking for a champion: resurrect log4j 1.x

Jan 8, 2022, at 4:34 PM, Andrew Purtell wrote: > > > > The Logging PMC is the hostile party here as far as I can tell, operating > > in defiance of the community of users that have made the points I have > just > > written here abundantly clear for years. > > The Loggi

Re: Looking for a champion: resurrect log4j 1.x

eep returning to the end of life designation in these discussions, but do not acknowledge that the users of this EOL version were deliberately stranded by incompatible API and configuration file formats. There is a reason we are stuck on Log4J 1. I wish you could just hear this, acknowledge it, and service

Re: Looking for a champion: resurrect log4j 1.x

> On Jan 8, 2022, at 4:34 PM, Andrew Purtell wrote: > > The Logging PMC is the hostile party here as far as I can tell, operating > in defiance of the community of users that have made the points I have just > written here abundantly clear for years. The Logging PMC is the own

Re: Looking for a champion: resurrect log4j 1.x

Answers below: > On Jan 8, 2022, at 17:34, Andrew Purtell wrote: > > Log4J 1 has known concurrency issues but many projects live with them or > work around them. For example, several "Big Data" Apache projects have been > fine with it, themselves internally highly c

Re: Looking for a champion: resurrect log4j 1.x

Log4J 1 has known concurrency issues but many projects live with them or work around them. For example, several "Big Data" Apache projects have been fine with it, themselves internally highly concurrent and performance sensitive. Log4J 1 might not be a Platonic ideal, but certainly good

Re: Looking for a champion: resurrect log4j 1.x

reasonably serious proposals of how anyone expects to do this without causing further mayhem in the future. — Matt Sicker > On Jan 8, 2022, at 14:32, Rohit Yadav wrote: > > Hi Matt, > > Thanks for replying. I think the main issues I found following the guide [1] > for Apache Cl

Re: Looking for a champion: resurrect log4j 1.x

Hi Matt, Thanks for replying. I think the main issues I found following the guide [1] for Apache CloudStack (ACS) are: - APIs are not backward compatible fully, certainly everywhere the imports have to be fixed - The config xml files are not fully compatible requiring some changes - Our

Re: Looking for a champion: resurrect log4j 1.x

CloudStack too uses > log4j 1.x and our use case is simply a logging library that 1.x just > satisfies. The effort to migrate to 2.x is not quick, at least in our initial > investigation and a migration may likely require huge effort in testing. > > Assuming this quick upgrade pat

Re: Looking for a champion: resurrect log4j 1.x

Hi all, I agree and extend support for Andrew's remarks. Apache CloudStack too uses log4j 1.x and our use case is simply a logging library that 1.x just satisfies. The effort to migrate to 2.x is not quick, at least in our initial investigation and a migration may likely require huge e

Re: Looking for a champion: resurrect log4j 1.x

Hello, I just came across this thread - same as Ralph, I currently don't mentor any podlings. However, I am still on the Logging PMC. On Thu, Dec 23, 2021, at 07:05, Vladimir Sitnikov wrote: > Ralph>I was busy > > The world is on fire with log4j, so if you have no time l

Re: clutch analysis part 1 failing: status pages not updating

des a json structure > which can be reused in a good way. It’s just that there will be additional > work. > > I doubt I’ll have time to address this before the weekend. > > Regards, > Dave > >> On Jan 4, 2022, at 1:36 PM, Wilfred Spiegelenburg >> wrote: &g

Re: clutch analysis part 1 failing: status pages not updating

ll be additional work. I doubt I’ll have time to address this before the weekend. Regards, Dave > On Jan 4, 2022, at 1:36 PM, Wilfred Spiegelenburg > wrote: > > I was trying to figure out why my update to the status page for YuniKorn was > not showing up. > I can see that the c

clutch analysis part 1 failing: status pages not updating

I was trying to figure out why my update to the status page for YuniKorn was not showing up. I can see that the clutch data had not been updated for a couple of days also [1]. The build emails [2] point to a failure since build 808 [3]. The news added to the Inlong status page before my

Re: Looking for a champion: resurrect log4j 1.x

Ralph>I was busy The world is on fire with log4j, so if you have no time left for 1.x, then, please, just let others do the maintenance. Ralph>My recollection was me saying if I had the code in a git repo getting it into a GitHub repo would be easy. I do not want to dilute "svn ->

Re: Looking for a champion: resurrect log4j 1.x

bridge is not perfect. For > > example, since hadoop is still on log4j 1.x, I need to add log4j12 bridge > > dependency if I want to run UTs based on hadoop mini cluster, and then I > > need to manually copy some code from log4j1 in order to make it work, > this > > is an example

<    1   2   3   4   5   6   7   8   >