[x] LICENSE/NOTICE files exist
> > [x] No unexpected binary files
> > [x] All source files have ASF headers
> > [x] Can compile from source on macOS(arm64)
> > I tried compiling the Java, JavaScript, and Rust packages, and they
> > all built successfully.
> >
> >
Looks great to me,
Xuanwo has been continuously active in the incubator and helped the
release of many podlings including Fury .
His experience in rust and opendal incubation would be a great help to Fury.
Looking forward to collaborating with Xuanwo.
Best regards,
Chaokun Yang
On Mon, May
first source
> for binding release votes is your mentors.
>
> Can you please ask your mentors to vote before asking the entire Incubator
> PMC?
>
> Thanks,
> Craig
>
> > On May 27, 2024, at 04:21, Shawn Yang wrote:
> >
> > Dear IPMC Members,
> >
>
.
Your feedback is crucial for ensuring the quality and adherence to
Apache's standards.
Thank you in advance for your help.
Best regards,
Chaokun Yang
On Thu, May 23, 2024 at 10:21 PM Shawn Yang wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache Fury(Incubating
Carry my no-binding +1.
Best Regards,
Chaokun Yang
On Thu, May 23, 2024 at 10:21 PM Shawn Yang wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache Fury(Incubating) v0.5.1-rc2.
>
> The Apache Fury community has voted and approved the release of Apache
Hello everyone,
This is a call for the vote to release Apache Fury(Incubating) v0.5.1-rc2.
The Apache Fury community has voted and approved the release of Apache
Fury(incubating) v0.5.1-rc2. We now kindly request the IPMC members
review and vote for this release.
Apache Fury(incubating) - A
Hi Tiago,
>From the current incubator release policy, you need to rename all npm
packages to apache-xxx before releasing. The packages released before
should be on to left intact.
I came across same issue when we release apache fury. In your case, most
packages starts with kie. Fury has similar
Hi all,
The Apache Fury(incubating) community is pleased to announce
that Apache Fury(incubating) 0.5.0 has been released!
Apache Fury(incubating) - A blazingly fast multi-language serialization
framework powered by JIT and zero-copy.
The release notes are available here:
Hi Incubator PMC,
The vote to release Apache Fury(incubating) v0.5.0-rc4 has passed with
3 +1 binding and 1 +1 non-binding votes, no +0 or -1 votes.
Binding votes：
- tison
- PJ Fanning
- Xuanwo
Non-Binding votes:
- Chaokun Yang
Vote thread:
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 re
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
Hi everyone,
I recorded a video about how to use Scanoss to audit the code.
Hope it can be useful for other people and podlings to inspect their code,
and make the release more efficient:
Screen Recording 2024-04-29 at 12.46.08.mov
Hi,
The release for Apache Fury(incubating) v0.5.0-rc3 is canceled.
We didn't include the benchmark code in the source release, but the
LICENSE file did contain the reference to benchmark code.
This has been fixed in [1]
1. https://github.com/apache/incubator-fury/pull/1562
We will propose a
hough this can be a good way to go, I notice that in this RC the tarball
> packages furyjs' code:
>
> 0.5.0-rc3/apache-fury-incubating-0.5.0-src/javascript
>
> I'd like to know the details about "we don't release furyjs in 0.5.0"
> because you seem to release furyjs'
; to Apache Fury also, like [2][3].
>
> [2] https://github.com/GreptimeTeam/greptimedb/pull/2653
> [3] https://github.com/GreptimeTeam/greptimedb/pull/3168
>
> Best,
> tison.
>
>
> Shawn Yang 于2024年4月25日周四 17:04写道：
>
> > Hi Justin,
> >
> > Thanks
Hi Justin,
Thanks for sharing this tool. I checked the code in Fury with this tool.
Here is the result:
1) [5][6] are osscan results.
2) Those files has duplication with package/lib/worker-host.js in
opensumi[7]
Opensumi relies on furyjs, so it packaged the code in apache fury into its
release
Hi Sebb,
The published install page[1] should look good now, could you check it
again?
1. https://fury.apache.org/docs/start/install
Best Regards,
Chaoun Yang
On Wed, Apr 24, 2024 at 3:44 PM sebb wrote:
> On Wed, 24 Apr 2024 at 08:29, Shawn Yang wrote:
> >
> > Hi
note near the end.
>
> On Tue, 23 Apr 2024 at 16:07, Shawn Yang wrote:
> >
> > I updated it in the PR
> > https://github.com/apache/incubator-fury-site/pull/112. Sorry for my
> last
> > reply, I forgot to put the PR link.
> >
> > On Tue, Apr 23, 2024 at 10:2
Hi Justin,
Thanks for helping review this release.
The MemoryBufferWritableChannel[5] and MockWritableChannel[6] was written
by me before we open-sourced Fury and
I submitted it to Ray in PR[8] ,which was planned to optimize zero-copy
serialization in Ray. I think it's OK to include it
here
I updated it in the PR
https://github.com/apache/incubator-fury-site/pull/112. Sorry for my last
reply, I forgot to put the PR link.
On Tue, Apr 23, 2024 at 10:22 PM sebb wrote:
> On Tue, 23 Apr 2024 at 14:05, Shawn Yang wrote:
> >
> > Hi Sebb,
> >
> > I updated the
locker.
> > > > >
> > > > > I would be very disappointed if the podling published the code
> > > > > *knowing* that the download page is missing or incorrect.
> > > > >
> > > > > > Best,
> > > > > > tis
-site/pull/111/
3. https://infra.apache.org/release-download-pages.html
On Mon, Apr 22, 2024 at 4:35 PM sebb wrote:
> On Sat, 20 Apr 2024 at 16:26, Shawn Yang wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating)
> v0.5.
thon.
> My local Python version is newer, which gave me some unexpected
> dependency issues.
> You guys might want to give more explicit guidance on environment
> requirements.
>
> refs:
> - https://github.com/nodejs/node-gyp/issues/2869
>
> Sincerely,
> Suyan
>
> S
Hello everyone,
This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc3.
The Apache Fury community has voted and approved the release of Apache
Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
review and vote for this release.
Apache Fury(incubating) - A
SD licensed, so just put the text in LICENSE
> 2. is Apache licensed, It’s a good idea to list that in the LICENSE file
> (but not required). It has no NOTICE file, so there is nothing to go in
> your NOTICE file.
>
> Kind Regards,
> Justin
>
> > On 13 Apr 2024, at
:
> On Sat, Apr 13, 2024 at 1:54 AM Shawn Yang
> wrote:
>
> > Dear Community,
> >
> > I'm fixing the license issue of Apache Fury to comply with ASF
> requirements
> > for the first release for Fury under ASF.
> >
> > Currently we borrowed some code fro
Dear Community,
I'm fixing the license issue of Apache Fury to comply with ASF requirements
for the first release for Fury under ASF.
Currently we borrowed some code from other projects such as
v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned
their license in our NOTICE
+1 (non-binding)
Thanks,
Chaokun
+1 non-binding
Best,
Chaokun Yang
+1 (non-binding)
Best regards,
Chaokun Yang
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
+1 (non-binding)
Best,
Chaokun Yang
Hi Greg,
Thanks for pointing this out. As of now, we do not have a formal document
that compares Fury with Apache Thrift and Avro. Here is a brief overview
of the differences:
1. Fury vs Thrift:
1) Thrift needs to define the IDL, use the thrift compiler to generate
code, then invoke the
32 matches
Mail list logo
