> ... this is caused by using Mac's built-in tar, ...
The ._ (and also .DS_Store) files are the mac meta files. We probably
should exclude them in maven assembly or remove them by a script/maven
plugin ?
Tsz-Wo
On Sun, Mar 23, 2025 at 3:37 AM Attila Doroszlai
wrote:
> Thanks Wei-Chiu for wor
Thanks for checking out the RC bits and feedback!
I'm dropping RC0 bits and making an RC1 that incorporates the changes.
It'll be built on a Red Hat Linux 8.8 with RocksDB native JNI tools and
with JDK8.
Expect to post a new thread once I finish up sanity checks.
On Sun, Mar 23, 2025 at 10:26 AM
I was concerned about the native rocksdb jni library than the Mac generated
meta files :)
The release build script should include -Drocks_tools_native to build it.
Probably better to repeat the build on a Linux box instead.
BTW, tools/fault-injection-service build is not managed by Maven. I'll sk
Thanks Wei-Chiu for working on the release.
> Source code and binary tarball:
> https://dist.apache.org/repos/dist/release/ozone/2.0.0-rc0/
RC should be added in dist/dev, not dist/release.
> I built on a Mac M3. Does it make any difference if I build on an x86 Linux?
On Linux, the binary tarba
I just realized my binary was built using JDK21.
openjdk version "21.0.1" 2023-10-17 LTS
OpenJDK Runtime Environment Zulu21.30+15-CA (build 21.0.1+12-LTS)
OpenJDK 64-Bit Server VM Zulu21.30+15-CA (build 21.0.1+12-LTS, mixed mode,
sharing)
Will this be a problem? Should I build with JDK8? Or even
> I'm not sure which KEYS file is the correct one -- the one under /release/
> or the one under /dev/?
release is the correct one. dev is for the case if "you are a
committer and not a PMC member".
-Attila
-
To unsubscribe, e-m
Absolutely,
well it's a huge release and I'm still processing the release note. It's
still very rough but here's a teaser:
https://docs.google.com/document/d/1fw3OUjLDRgS-L5R1JmSa4mT770ZBMrB6enMEoXhCQSY/edit?usp=sharing
This release is comprised of 1691 issues fixed, which includes 11 New
Feature
Thanks for working on this Wei-Chiu. Can you share the planned release
notes for this release to help in the voting process? I'm not entirely sure
which features did or did not make the cut, or what our
compatibility guarantees are with the 1.x line.
Ethan
On Fri, Mar 21, 2025 at 7:02 PM Wei-Chiu
Correction:
I appended my PGP key here:
https://dist.apache.org/repos/dist/release/ozone/KEYS
I'm not sure which KEYS file is the correct one -- the one under /release/
or the one under /dev/?
On Fri, Mar 21, 2025 at 3:42 PM Wei-Chiu Chuang wrote:
> Hi Ozone community,
>
> Please try out and cas
