Hi,
+1 (binding)
I checked only the source release:
- incubating in name
- signature and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE are good
- No unexpected binary files
- Hard to tell if any files are missing headers due to large number of Json
files
- Didn’t compile from source
It a
Hi,
+1 (binding)
I checked:
- incubating in name
- signatures and hashes are correct
- LICENSE and NOTICE are fine
- No binary files in release
- All source files have ASF header
- Can “compile"
Thanks,
Justin
-
To unsubscribe,
Hi Justin,
- Good point about the community. We know it’s a point we have to work
generally speaking.
- +1 about the "inexperience with open source" section, I will add some content.
- Agree to start only with dev mailing list
- we are kindly asking for gitbox repo (not svn). It’s in the proposal
Hi,
-1 (binding) as LICENSE issues mentioned on the last RC have not been fixed and
this release is not using the work in progress disclaimer.
I checked:
- incubating in name
- LICENSE is missing 3rd party license information and full text of licenses is
not include
- NOTICE incorrectly mentio
I had the same questions Justin mentioned wrt gossip and relayer but
forgot to mention that.
One approach could be to have your artifacts split into sources and
distributions subdirectories (or similar names).
Cheers, Paul.
On Sun, Mar 15, 2020 at 5:37 PM Justin Mclean
wrote:
> Hi,
>
> +1 (bin
Thanks, Justin!
Do you have a link that explains more about where to put what for LICENSE and
NOTICE?
>From what I'd understood LICENSE was to remain the pure Apache License 2.0
>text and NOTICE should contain any reference to any other copywritten material
>contained within the repo--though i
Hi,
> Do you have a link that explains more about where to put what for LICENSE and
> NOTICE?
Yep [1].
> From what I'd understood LICENSE was to remain the pure Apache License 2.0
> text and NOTICE should contain any reference to any other copywritten
> material contained within the repo--tho
Hi all,
The SAMOA community has voted to promote a release candidate to a
full-release.
The vote thread can be found at:
https://lists.apache.org/thread.html/r9ee34c67da99269915485635ae9c86e158fb9e149727e699d3990e23%40%3Cdev.samoa.apache.org%3E
and the result thread at:
https://lists.apache.org/
Dear IPMC,
Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
Deletes and Incrementals. Apache Hudi (incubating) manages storage of
large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
FileSystem compatible storage) and provide ability to query them.
The Apache H
transferring my vote from dev@hudi
+1 binding
On Sun, Mar 15, 2020 at 10:58 PM vino yang wrote:
> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
> Deletes and Incrementals. Apache Hudi (incubating) manages storage of
> large analytical datasets on DFS (C
+1
Best wishes.
在 2020/3/15 上午8:40，“ShaoFeng Shi” 写入:
+1 (binding), Gook luck!
Best regards,
Shaofeng Shi 史少锋
Apache Kylin PMC
Email: shaofeng...@apache.org
Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail
+1 (binding) with some caveats.
I checked:
* Incubating in name
* DISCLAIMER exists
* LICENSE and NOTICE okay (copyright end year in NOTICE needs a bump I
would suspect)
* Signatures okay
* Checksums okay
My understanding is that the KEYS file for your project is expected in:
https://dist.apach
12 matches
Mail list logo
