Unexpected, maybe we
need submit a JIRA ticket to enable it)
Hope my explanation is clear~
Imba Jin
On 2024/05/08 14:53:13 Daniel Gruno wrote:
> On 5/8/24 09:45, sebb wrote:
> > On Wed, 8 May 2024 at 15:15, Daniel Gruno wrote:
> >>
> >> On 5/8/24 03:20, Sheng Wu wrote:
+1 (non-binding)
In addition, I found that the new GitHub repo created through the
"selfserve.apache.org" page before, the default is not configured to
automatically jump the 'incubator' address(return 404), which caused some
unexpected problems..
Imba Jin
On 2024/05/08 00:31:23 t
+1 (non-binding)
Good luck~
On 2024/03/15 05:57:00 Yu Li wrote:
> Hi All,
>
> With positive feedback from the proposal discussion [1], I am starting
> this official vote to accept GraphAr into the Incubator. Here is the
> proposal:
>
>
+1 (non-binding)
Good luck~
On 2024/03/03 01:44:24 Justin Mclean wrote:
> Hi,
>
> Following on from the discussion of the Amoro proposal [1][2], let's vote on
> having it join the Incubator.
>
> Please cast your vote:
>
> [ ] +1, have it join the Incubator as an incubating project
> [ ] +0,
cies.
Best regards,
Imba Jin (from Apache HugeGraph)
On 2024/03/01 12:36:12 Yu Li wrote:
> Hi All,
>
> I would like to propose GraphAr [1] as a new apache incubator project,
> and you can find the proposal [2] for more details.
>
> GraphAr is an open source and language
h.apache.org/cn/docs/changelog/hugegraph-1.0.0-release-notes/
(CN)
Website: https://hugegrapgh.apache.org/
Linkis Resources:
- Issue: https://github.com/apache/incubator-hugegrapgh/issues
- Mailing list: d...@hugegrapgh.apache.org
Imba Jin
On behalf of Apa
the rest of the developer community
Shiming Zhang(ming)
Vote thread:
https://lists.apache.org/thread/61s5zd74hglcrn9w46lj8qkxhdw6t54o
Thanks for reviewing and voting for our release candidate.
We will proceed with publishing the approved artifacts and sending
out the announcement soon.
Imba Jin
lled.
> - LICENSE file and DISCLAIMER file look good to me.
> - No unexpected binary in source tar ball.
> - files have ASF license headers if needed, and don't have if no need.
>
> Good luck
>
> > On Feb 13, 2023, at 20:06, Imba Jin wrote:
> >
> > Hello
Hello Incubator Community,
This is a call for a vote to release Apache HugeGraph(Incubating)
version 1.0.0-rc2
The Apache HugeGraph community has voted on and approved a proposal
to release Apache HugeGraph(Incubating) version 1.0.0-rc2
In this release, we fixed a string of license problems
Thanks for the reply, we choose the "loose license" in the multiple choices,
and now we only keep one (selected) license instead of list them all in
'LICENSE' file.
Could you help us to review the correctness of the latest update?[1] After
confirmation, we will modify all other repos soon
1.
Thanks a lot for the review & suggestion
I just send a CANCEL mail & will also address the GPL & binary problems before
2rd voting
On 2023/01/17 07:21:30 Justin Mclean wrote:
> Hi,
>
> -1 (binding)
>
> In addition to the issues mentioned I can also see GPL licensed software
> mentioned [1]
Hello Incubator Community,
I'm cancelling this vote
https://lists.apache.org/thread/b0d3dsy2v6c4n7p5o4br213n1wrzmccx
because of license issues.
I'll fix them and start the round 2 vote process soon.
The details of the modifications are as follows:
1. Remove the copyright from all source file
/tree/1.0.0
Release notes:
• https://hugegraph.apache.org/docs/changelog/hugegraph-1.0.0-release-notes/
Due to this is the first release version, we have 3 people to participate in it.
The GPG user ID(s): Imba Jin, vaughn, coderzc, corresponding to
j...@apache.org, vau...@apache.org, zhaoc
Hi Willem,
It's OK, thanks for helping to update it, we'll move doc repo out of toolchains.
And also thanks for updating the mailing list.
___Imbajin @ HugeGraph Team
It makes sense for the Hugegraph client part of code.
I just we still keep the document repo seperatly, as it
Hi Calvin,
Thanks for the advice.
After the Apache mail is granted, we will gradually update the address of
mailing list.
Imbajin @ HugeGraph Team
Thanks to the concern for the release with HugeGraph Toolchain repo, after
listened to the dev user voice, we think merge them to one will
help the community work/contribute for them better. (Due to their function is
similar users don't need to download multiple repos)
And regard to the
16 matches
Mail list logo