>I would propose to talk with logging PMC first
I did exactly that, and they did not listen. They have no will to keep
releasing 1.x versions.
At the same time, they do not allow others to release log4j:log4j:1.x
versions.
I'm waiting for the response by Logging PMC chair Ron once again:
ht
Romain,
Romain>for now the thread is looking for options which are not needed from
my window
It was the Logging PMC team who suggested I should re-incubate log4j 1.x.
Romain>1. where is the patch needed to fix the desired CVE? - must be
compatible
with current SVN trunk
The current SVN
rit :
>
> ok, so let's try to not create an endless thread:
>
> 1. where is the patch needed to fix the desired CVE? - must be compatible
> with current svn trunk
> 2. please attach it to a ticket (or multiple if there are multiple fixes)
> like LOG4J2-3219
> 3. if it d
ok, so let's try to not create an endless thread:
1. where is the patch needed to fix the desired CVE? - must be compatible
with current svn trunk
2. please attach it to a ticket (or multiple if there are multiple fixes)
like LOG4J2-3219
3. if it does not get applied and PMC is opposed to get
Matt>Nobody in the Logging PMC is blocking a release here.
Matt, thanks for the reply, however, it is false :(
I see you are positive, however, many more replies were quite negative.
Ralph Goers says: "We’ve stated several times that we don’t think
resurrecting Log4j 1.x permanently i
Sent from my iPhone
> On Dec 21, 2021, at 5:13 AM, Romain Manni-Bucau wrote:
>
> Le mar. 21 déc. 2021 à 12:33, Enrico Olivelli a
> écrit :
>
>> Vladimir,
>> I totally support this proposal.
>>
>> Which are actually the steps we need to cut
Sent from my iPhone
> On Dec 21, 2021, at 3:33 AM, Enrico Olivelli wrote:
>
> Vladimir,
> I totally support this proposal.
>
> Which are actually the steps we need to cut a release of log4j 1.x ?
> - establish an Apache project ?
> - do the fix
> - cut a re
Hi,
Have you discussed the approach you outlined with the logging PMC? It seems to
me the idea of a drop in jar that allows log4j 1 over log4j 2 is an ideal
product for that PMC to support.
All the best,
Dave
Sent from my iPhone
> On Dec 21, 2021, at 8:22 PM, 张铎 wrote:
>
> I'
I'm the one who migrated HBase from log4j to log4j2, and still tries to
migrate hadoop but still can not find a suitable upgrading path...
For me, I do not prefer we release a new log4j 1.x, it has been EOL for
many years, we should encourage people to upgrade to a newer logging
framework. FWIW
ion to this. If the log4j 2.x configuration files
were compatible _enough_ with 1.x then taking this position would be
understandable. However, because they are not compatible in the way that
users require -- and the backwards compatibility is still marked as
'experimental', even -- it is not gr
of make or Ant?
--
Matt Sicker
> On Dec 21, 2021, at 07:13, Romain Manni-Bucau wrote:
>
> Le mar. 21 déc. 2021 à 12:33, Enrico Olivelli a
> écrit :
>
>> Vladimir,
>> I totally support this proposal.
>>
>> Which are actually the steps we need to cut
Le mar. 21 déc. 2021 à 12:33, Enrico Olivelli a
écrit :
> Vladimir,
> I totally support this proposal.
>
> Which are actually the steps we need to cut a release of log4j 1.x ?
> - establish an Apache project ?
>
1. Send a patch to apply on
http://svn.apache.org/repos/asf/l
Vladimir,
I totally support this proposal.
Which are actually the steps we need to cut a release of log4j 1.x ?
- establish an Apache project ?
- do the fix
- cut a release
Can this be done inside another Apache Project who "adopts" the log4j
sources if the Logging Project doesn't
>Just wondering, is it even fulfilling the criteria of incubation?
I believe, the world does not need "active development in log4j 1.x"
nowadays.
What everybody needs from log4j 1.x is to fix security issues, fix
outstanding issues (if any),
keep the project buildable (e.g. avoid u
What are the concerning security vulnerabilities in log4j 1 and the
severity level?
I saw one mentioned in the thread which apparently redhat had fixed (with
socket stream deserialization)
On Mon, Dec 20, 2021 at 3:56 PM Martin Gainty wrote:
> i would ping the original author ceki gu
in objective.
ceki.blogspot.com
Best Regards,
martin-
From: Jungtaek Lim
Sent: Monday, December 20, 2021 4:26 PM
To: general@incubator.apache.org
Subject: Re: Looking for a champion: resurrect log4j 1.x
Just wondering, is it even fulfilling the criteria of incubation? Have
th
at 10:51 PM John D. Ament
wrote:
> On Mon, Dec 20, 2021 at 8:42 AM Romain Manni-Bucau
> wrote:
>
> > Guess there are 4 options:
> >
> > 1. resurrect log4j1 and let it die again
> > 2. do a log4j1 release for the CVE under logging umbrella (as a
> subpro
On Mon, Dec 20, 2021 at 8:42 AM Romain Manni-Bucau
wrote:
> Guess there are 4 options:
>
> 1. resurrect log4j1 and let it die again
> 2. do a log4j1 release for the CVE under logging umbrella (as a subproject)
> - after all log4j1 belongs to logging as a subproject al
Guess there are 4 options:
1. resurrect log4j1 and let it die again
2. do a log4j1 release for the CVE under logging umbrella (as a subproject)
- after all log4j1 belongs to logging as a subproject already (
https://logging.apache.org/dormant.html)
3. the log4j1-log4j2 bridge (but agree
as a standalone
podling and keeping the Incubator as sponsor rather than Logging. See [1]
for some details on those notes. The incubator would be responsible for
voting on releases, receiving notices for new PPMC members, etc regardless
of who is the sponsor. Given enough contributors and a diverse contributor
>Do you have "facts" (like message on mailing list) ?
I am not sure what you mean.
For example:
1) Ralph Goers says the existing committers did not touch 1.x code a lot:
https://lists.apache.org/thread/j6zrdp1d148qpkg0g7x3cc41o070oq6n
Ralph>Virtually all of the contributors
est contributors should focus on polishing log4j 1->2
compatibility layer.
Making the compatibility 100% correct is hard, so I believe forcing
everybody to upgrade is not the right thing to do.
JB>Anyone can propose new releases on any branches (including old ones).
log4j pmc denies migrati
JB>Anyone can propose new releases on any branches (including old ones).
JB>If you need my support/help on this, please let me know.
I and the other contributors tried to suggest PRs, however, log4j pmc
actively denies them.
They suggest contributors should focus on polishing log4
Hi
I don’t think you need the incubator there. You can propose to log4j pmc to
move forward on log4j 1.x.
Anyone can propose new releases on any branches (including old ones).
If you need my support/help on this, please let me know.
Just my €0.01 ;)
Regards
JB
> Le 20 déc. 2021 à 08
Hi,
I want to resurrect log4j 1.x to fix well-known security issues.
I'm looking for the champion and committers.
log4j 1.x is a wildly used logging library, so releasing a secured version
would silence CVE warnings
all over the world, and it would enable users to focus on more relevant
tasks
Hi all,
The vote for releasing Apache Teaclave TrustZone SDK (incubating)
v0.2.0-rc.1 is closed.
We received 7(+1) non-binding votes and 1(-1) binding vote.
Since there are some issues about license review, we will work on this
and prepare for the second release candidate later. Thanks
Hi,
> Basically, there are two issues in the release tar bar:
> 1. We are using a customized Rust's standard library and include
> modified sources and other upstream code in our codebase.
> 2. We also include code of OP-TEE libraries as our vendored
> third-party libraries.
Hi Justin,
Thanks for the careful screening.
Basically, there are two issues in the release tar bar:
1. We are using a customized Rust's standard library and include
modified sources and other upstream code in our codebase.
2. We also include code of OP-TEE libraries as our vendored
third
Hi,
Sorry but -1 (binding) due to incompatible licenses in source release and those
licenses not mentioned. A WIP disclaimer isn’t a blanket exception and you need
to note what the issues are and inform the used of what licenses are
incompatible. Please see [4]
When voting on releases, it’s
+1
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
>
+1
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
>
+1
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
>
+1
Thanks!
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and appr
+1
Thanks
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and appr
+1
I have done the following checks.
- DISCLAIMER is OK.
- LICENSE and NOTICE are OK.
- Code compiled successfully, despite some warnings on unused variables.
- All test cases passed.
Best,
Zhaofeng
On Mon, Nov 29, 2021 at 10:57 AM Mingshen Sun wrote:
> Hi all,
>
> I am pleased to b
+1
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
>
+1
On 2021/11/29 18:56:49 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
>
Hi all,
I am pleased to be calling this vote for the second release of
Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
Rundong Zhou
t;
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
> release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
&g
1
Hi all,
I am pleased to be calling this vote for the second release of
Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
Rundong Zhou
e second release of
> > Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
> > Rundong
On Sun, 28 Nov 2021 at 06:08, Mingshen Sun wrote:
>
> Hi all,
>
> I am pleased to be calling this vote for the second release of
> Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
Hi all,
I am pleased to be calling this vote for the second release of
Apache Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate 1).
The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Yuan Zhuang, Rong Fan,
Rundong Zhou
Hello Everyone,
The vote to release Apache Hop (incubating) 1.0.0 - RC1 has passed.
+1 (binding):
- Julian Hyde
- François Papon
- Kevin Ratnasekera
- Xun Liu
- 朱辉
+1 (non-binding)
- 独孤求败
Thank you for reviewing this release candidate.
Cheers,
Hans
Great. Then hereby the vote to release Apache Annotator (incubating)
0.2.0 has PASSED with 3 binding +1 votes (and no other votes) from:
- Xun Liu
- Nick Kew
- Benjamin Young
Thank you for your help. We will proceed with publishing the release and
announcement.
On behalf of the team,
— Gerben
Hey - I’ve reviewed the VOTE thread and there have been 2 +1s from the 3
Podling Mentors.
Since Xun Liu VOTED +1 and since August 14 is an IPMC member.
I think this passes.
> On Aug 26, 2021, at 7:12 PM, Xun Liu wrote:
>
> hi, Benjamin
>
> Maybe you need to in
hi, Benjamin
Maybe you need to invite the mentor of the Annotator project to vote. :-)
Xun Liu
Best regards,
On Fri, Aug 27, 2021 at 12:01 AM Benjamin Young
wrote:
> Hi all,
>
> Here's a formal +1 (binding) vote from an IPMC member. I'm not sure, yet,
> what part of this process
Hi all,
Here's a formal +1 (binding) vote from an IPMC member. I'm not sure, yet, what
part of this process we're doing incorrectly, but it stays awfully quiet when
we post here...and I believe we need 2 more IPMC votes to get this officially
released?
As Gerben mentioned last month (see
Thanks, Xun.
Yes, I think this is not a blocking issue (correct me if I'm wrong),
and I will work on this before the next release.
On Mon, Aug 23, 2021 at 7:20 PM Xun Liu wrote:
>
> Hi mingshen,
>
> Please don't forget to add the `NOTICE` and `DISCLAIMER` in the [1] sub
> re
Hi mingshen,
Please don't forget to add the `NOTICE` and `DISCLAIMER` in the [1] sub
repo of incubator-teaclave. Thanks.
[1] https://github.com/apache/incubator-teaclave-sgx-sdk
Xun Liu
Best regards
On Tue, Aug 24, 2021 at 1:54 AM Mingshen Sun wrote:
> Thanks to everyone that participa
Hi all,
Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.3.0 Release Candidate 1 in general@incuabator
is now closed.
Vote thread:
https://lists.apache.org/thread.html/r018fb18270819082d15b106a9261144c8b27144cef992b68db537597%40
Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.3.0 Release Candidate 1 is now closed.
The vote PASSED with 5 binding +1, 0 non binding +1 and 0 -1 votes:
Binding votes:
- Gordon King
- Yulong Zhang
- Xun Liu
- Hongbo Chen
- Rundong Zhou
I
+1
On 2021/08/20 18:28:53, Hongbo Chen wrote:
> +1.
> This release works well on my side and I can run examples sucessfully.
>
> Thanks,
> Hongbo
>
> On 2021/08/20 05:15:16, Mingshen Sun wrote:
> > Hi all,
> >
> > I am pleased to be calling this v
+1.
This release works well on my side and I can run examples sucessfully.
Thanks,
Hongbo
On 2021/08/20 05:15:16, Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the third release of
> Apache Teaclave (incubating) 0.3.0 (release candidate 1).
>
+1 (binding) from me,
I have checked the following items:
[√] Are release files in correct location?
[√] Do release files have the word incubating in their name?
[√] Are the digital signature and hashes correct?
[√] Does DISCLAIMER-WIP file exist?
[√] Do LICENSE and NOTICE files exists
+1
On 2021/08/20 05:15:16 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the third release of
> Apache Teaclave (incubating) 0.3.0 (release candidate 1).
>
> The Apache Teaclave (incubating) community has voted and approved the
> release, with fi
It is verified from my side and looks good, +1 (binding), thanks.
On 2021/08/20 05:15:16 Mingshen Sun wrote:
> Hi all,
>
> I am pleased to be calling this vote for the third release of
> Apache Teaclave (incubating) 0.3.0 (release candidate 1).
>
> The Apache Teaclave (incubat
Hi all,
I am pleased to be calling this vote for the third release of
Apache Teaclave (incubating) 0.3.0 (release candidate 1).
The Apache Teaclave (incubating) community has voted and approved the
release, with five +1 votes from IPMC members (Pei Wang, Yulong Zhang,
Rundong Zhou, Tongxin Li
+1 (non-binding) from me, I have checked the following items:
- Incubating in name
- NOTICE is fine
- DISCLAIMER-WIP exists
- All links are valid
- All ASF files have ASF headers
- RUN: yarn install & yarn build & make check
- GPG signature okay.
- Checksums okay.
- Apache Ra
ble here:
<https://dist.apache.org/repos/dist/dev/incubator/annotator/source/0.2.0/rc.1>
Steps to verify the contents are described in our wiki:
<https://github.com/apache/incubator-annotator/wiki/Testing-a-Source-Release>
Within the project, we got three +1 votes by PPMC members and no
Thank you to everyone who participated in the vote. The voting is now
closed and it has passed.
Binding votes:
1: +1 votes
- Ming Wen
- Kevin Ratnasekera
- Justin Mclean
0 : 0 votes
0: -1 votes
HI,
+1 binding
I checked:
- incubating in name
- signatures and hashes are fine
- LICENSE and NOTICE are fine
- no unexpected binary files in the releases
- all ASF files have ASF headers
- didn’t compile
Thanks,
Justin
Hi,
If we can get one more +1 vote on this RC we can release.
If anyone has the time please help with the vote.
On Wed, May 19, 2021 at 1:48 PM Josh Fischer wrote:
> I am sending this again as I missed the vote and vote result thread links in
> the last email.
>
>
> Hi,
on this incubator
release.We only have 2 binded approvals as we have not heard from one
of our mentors as of late.
The results of the Release Candidate 1 votes are below:
- Vote Thread
https://lists.apache.org/thread.html/r154ab280a85863ef51ac6b627b306596fae84c50cab37ac3f25d052c%40%3Cdev.heron.apache.org
as of late.
The results of the Release Candidate 1 votes are below:
- Binded Approvals: 2
* Ming Wen
* Kevin Ratnasekera
Hello Heron Community,
This is a call for a vote to the 1st release candidate for Apache Heron,
version 0.20.4-incubating*.*
We request project mentors (binded) as well
Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.2.0 Release Candidate 1 is now closed.
The vote PASSED with 7 binding +1, 0 non binding +1 and 0 -1 votes:
Binding votes:
- Yu Ding
- Furkan Kamaci
- Rundong Zhou
- Pei Wang
- Tongxin Li
- Yiming
Thanks to everyone that participated. The vote to release Apache
Teaclave (incubating) version 0.2.0 Release Candidate 1 is now closed.
The vote PASSED with 7 binding +1, 0 non binding +1 and 0 -1 votes:
Binding votes:
- Yu Ding
- Furkan Kamaci
- Rundong Zhou
- Pei Wang
- Tongxin Li
- Yiming
Hi,
I’ll try to compile it again. For the incorrect year in NOTICE, fixing it
at next release is fine as Justin mentioned.
Kind Regards,
Furkan KAMACI
On 1 Mar 2021 Mon at 10:42 Justin Mclean wrote:
> HI,
>
> > Also, for the incorrect year in NOTICE. Should I fix it in this
HI,
> Also, for the incorrect year in NOTICE. Should I fix it in this
> release (and vote for another candidate) or fix it before the next
> release version? Thanks.
Fix it in the next release is fine IMO.
Thanks,
Justin
-
To
Hi Furkan,
I tried to compile it in Docker for macOS with 8 GB memory and can
compile it successfully (but pretty slow).
Can you verify that the `apache-teaclave-0.2.0-rc.1-incubating/keys`
directory exists? If possible, it's recommended to compile with docker
on Linux.
Also, for the incorrect
Alright, finally finished building and running tests. All passed after
upping the memory limits to 8 GB, thought that might be overkill.
+1
On Sun, 28 Feb 2021 at 16:43, Yiming Jing wrote:
>
> +1 approve
>
> On 2021/02/26 18:26:28, Mingshen Sun wrote:
> > Dear community,
>
+1 approve
On 2021/02/26 18:26:28, Mingshen Sun wrote:
> Dear community,
>
> This is a call for a vote to release Apache Teaclave (incubating)
> version 0.2.0. This is the second Apache release since Teaclave
> entered the incubator.
>
> The Apache Teaclave (incubating
Hi Mingshen,
Yes, I’ve tried it on macOS.
Kind Regards,
Furkan KAMACI
On 28 Feb 2021 Sun at 23:46 Tongxin Li wrote:
> +1
>
> On 2021/02/28 20:12:23, Pei Wang wrote:
> > +1
> >
> > On 2021/02/26 18:26:28 Mingshen Sun wrote:
> > > Dear community,
&
+1
On 2021/02/28 20:12:23, Pei Wang wrote:
> +1
>
> On 2021/02/26 18:26:28 Mingshen Sun wrote:
> > Dear community,
> >
> > This is a call for a vote to release Apache Teaclave (incubating)
> > version 0.2.0. This is the second Apache release since T
ror-format=json --json=diagnostic-rendered-ansi,artifacts
> > --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
> > metadata=39ca99cb54d77a3c -C extra-filename=-39ca99cb54d77a3c
> > --out-dir /teaclave/build/target/trusted/debug/deps -L
> > dependency=/teaclave/build/targ
+1
On 2021/02/26 18:26:28 Mingshen Sun wrote:
> Dear community,
>
> This is a call for a vote to release Apache Teaclave (incubating)
> version 0.2.0. This is the second Apache release since Teaclave
> entered the incubator.
>
> The Apache Teaclave (incubating) community h
+1
Regards,
Rundong
On 2021/02/28 20:09:39, Mingshen Sun wrote:
> Hi Matt,
>
> For your case, I believe it is because of the memory limit
> (out-of-memory) of Docker for macOS. The Rust compiler needs more
> memory than others.
>
> Best,
> Mingshen
>
>
>
ts allow
> --cfg test_mode` (signal: 9, SIGKILL: kill)
> /usr/bin/ld: cannot find -lteaclave_authentication_service_enclave
> collect2: error: ld returned 1 exit status
> CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
> recipe for targe
/bin/ld: cannot find -lteaclave_authentication_service_enclave
collect2: error: ld returned 1 exit status
CMakeFiles/sgxlib-teaclave_authentication_service.dir/build.make:57:
recipe for target 'CMakeFiles/sgxlib-teaclave_authentication_service'
failed
make[2]: *** [CMakeFiles/sgxlib
is not checkout.
I'll fix this in the next release.
Best,
Mingshen
On Sat, Feb 27, 2021 at 12:30 AM Furkan KAMACI wrote:
>
> Hi,
>
> +1 from me (I have notes below).
>
> I checked:
>
> - Incubating in name
> - DISCLAIMER-WIP exists
> - LICENSE is fine
> - NO
Hi,
+1 from me (I have notes below).
I checked:
- Incubating in name
- DISCLAIMER-WIP exists
- LICENSE is fine
- NOTICE has *incorrect* *year* which should be fixed
- No unexpected binary files
- Checked PGP signatures
- Checked checksums
I got that error while compiling the project:
Digest
+1 approve
On 2021/02/26 18:26:28, Mingshen Sun wrote:
> Dear community,
>
> This is a call for a vote to release Apache Teaclave (incubating)
> version 0.2.0. This is the second Apache release since Teaclave
> entered the incubator.
>
> The Apache Teaclave (incubating
Dear community,
This is a call for a vote to release Apache Teaclave (incubating)
version 0.2.0. This is the second Apache release since Teaclave
entered the incubator.
The Apache Teaclave (incubating) community has voted and approved the
release, with four +1 votes from IPMC members (Pei Wang
Thanks for the votes!
On Wed, Aug 26, 2020 at 2:58 PM Felix Cheung wrote:
> +1 binding
>
> - incubating in name
> - signature and hash are fine
> - tarball (see note)
> the file unpacks into the current and not a subdirectory, is a bit strange
> - DISCLAIMER is fine
&
+1 binding
- incubating in name
- signature and hash are fine
- tarball (see note)
the file unpacks into the current and not a subdirectory, is a bit strange
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
- build from source
+1 binding
1. incubating in name
2. download link correct
3. LICENSE, NOTICE and DISCLAIMER exist
4. ASC checked
5. sha512 exists.
Good luck.
Sheng Wu 吴晟
Twitter, wusheng1108
Yi Shen 于2020年8月24日周一 下午5:21写道：
> Thanks, Dave.
>
> We still need 2 more votes.
>
> Thanks a lot.
>
Thanks, Dave.
We still need 2 more votes.
Thanks a lot.
On Wed, Aug 19, 2020 at 2:19 AM Dave Fisher wrote:
> +1 (binding)
>
> Incubating in name
> Verified signature and checksum
> LICENSE checked
> NOTICE checked
> DISCLAIMER checked
> Rat Check passed
>
>
+1 (binding)
Incubating in name
Verified signature and checksum
LICENSE checked
NOTICE checked
DISCLAIMER checked
Rat Check passed
Regards,
Dave
> On Aug 9, 2020, at 8:57 PM, Yi Shen wrote:
>
> Dear IPMC
>
> I am pleased to be calling this vote for the release of Apache EChart
>
>> Dear IPMC
>>
>> I am pleased to be calling this vote for the release of Apache ECharts
>> (incubating) 4.9.0 (release candidate 1).
>>
>> Apache ECharts community has voted and approved the release.
>>
We still need 3 binding votes on this release. Can anyone help vote?
Thanks!
On Mon, Aug 10, 2020 at 11:57 AM Yi Shen wrote:
> Dear IPMC
>
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.9.0 (release candidate 1).
>
> Apache ECharts c
Dear IPMC
I am pleased to be calling this vote for the release of Apache ECharts
(incubating) 4.9.0 (release candidate 1).
Apache ECharts community has voted and approved the release.
Vote thread:
https://lists.apache.org/thread.html/r67639d86c9b5944b1804fca86939052978df9594b45bc0d6474b9fb6%40
+1 (binding)
I checked:
1. Signature and Hashed are good.
2. Release commit and Tag are good.
3. LICENSE and NOTICE file are good for me.
4. DISCLAIMER is included.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, May 13, 2020 at 4:24 PM SHUANG SU wrote:
>
> I am p
Hi,
I ran it again and it worked no issues, sorry no idea what the issue was first
time.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
Hi Justin, thanks for the check!
I can compile from source successfully. Do you meet any errors when using
`npm install` to install dependencies?
On Fri, May 22, 2020 at 1:34 PM Justin Mclean
wrote:
> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signature
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are fine
- LICENSE and NOTICE are fine
- DISCLAIMER exists
- No unexpected binary files
- All ASF file have ASF headers
I was unable to get it to “compile” but that is likely my setup it was
complaining:
Error: Cannot
4.8.0 (release candidate 1).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/rebb8453baeeb21eaaa27a4dfc278413b6be0b1cf6850e50a0c3fc61e%40%3Cdev.echarts.apache.org%3E
>
> Results thread:
>
>
I am pleased to be calling this vote for the release of Apache ECharts
(incubating) 4.8.0 (release candidate 1).
Apache ECharts community has voted and approved the release.
Vote thread:
https://lists.apache.org/thread.html/rebb8453baeeb21eaaa27a4dfc278413b6be0b1cf6850e50a0c3fc61e%40
+1 (binding)
I checked:
- Download links are valid.
- Checksums and PGP signature are valid.
- DISCLAIMER file is included.
- Both LICENSE and NOTICE files are just fine.
- No binary file in the source.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Mar 6, 2020 at 5:12 AM SHUANG SU
+1 binding
Checked
1. ASC
2. incubating in name
3. LICENSE and NOTICE exist
4. sha512 exists.
Sheng Wu 吴晟
Twitter, wusheng1108
SHUANG SU 于2020年3月6日周五 上午5:12写道：
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.7.0 (release candidate 1).
>
201 - 300 of 761 matches
Mail list logo
