Repository navigation
[Release] 18.3.0 #723
Description
Activity
- pinned this issue
on Apr 22, 2025 @wgtmac as said on the mailing list, let me do a quick pass 😄. Thanks !
Reacted by Gang WuI'll do #587 but it's for release manager. We don't need to add it to 18.3.0.
I'll merge #718 today for 18.3 as @martin-traverse has been plugging away at the Avro improvements for a while
Otherwise, I went through issues/PRs and made sure they had a milestone attached. I don't think there's anything else we need, maybe we should get the current round of dependabot updates done, and I assume JB will want to fix up LICENSE/NOTICE
Reacted by Martin Traverse@jbonofre Is there anything that I can help with the check? Do you want to check the license and notice file?
@jbonofre any update/can we help?
I've asked about this before but is it possible to automate the license/notice checks? Or at least report on possible things we should update?
FYI, I'm reviewing the last updates, and I will create a PR about
LICENSE/NOTICE(after all updates). Then we will be good to go with the release. @wgtmac I will keep you posted.Reacted by David Li and Gang WuFYI, integration CI breakage is apache/arrow#46334
https://mvnrepository.com/artifact/io.grpc/grpc-netty/1.72.0
It seems gRPC itself hasn't updated to 4.2.x. I think we should stay on 4.1.x until gRPC upgrades and then upgrade them together. (We should perhaps instruct dependabot to group their updates together.)
1 remaining item
@wgtmac yup it's good for me. Thanks !
Created PR to bump version: #741
I have failed three times (for different targets) for uploading the artifacts to the staging repository due to bad network condition.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy-file (default-cli) on project arrow-java-root: Failed to deploy artifacts: Could not transfer artifact org.apache.arrow.gandiva:arrow-gandiva:jar.asc:18.3.0 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): Remote host terminated the handshake: SSL peer shut down incorrectly -> [Help 1]I tried to modify the script to resume the upload process but not sure if it has any side effect. I will try them again this weekend. If I cannot make it, could anyone help me create the RC?
I'll do it.
FYI: Our script already has 10 retries:
arrow-java/dev/release/release_rc.sh
Line 177 in 8e84e4c
args+=(-DretryFailedDeploymentCount=10) FYI: We can re-upload many times. We can remove failed uploads at https://repository.apache.org/#stagingRepositories .
Reacted by Gang WuFYI: We can't resume an upload with
mvn deploy:deploy-fileinterface. Becausemvn deploy:deploy-fileuses a session (?) that is created automatically. We can't reuse the auto created session.I just modified
release_rc.shto only doRELEASE_UPLOADto upload packages and it finally worked by creatingorgapachearrow-1182to the staging repository.Sent a vote for 18.3.0 RC2: https://lists.apache.org/thread/43nl349xgtgq18z5sp95mjkxov6m32qr
I have announced the release: https://lists.apache.org/thread/g620vmrg3n6v2nd8ny47blyvnomhol3t and https://arrow.apache.org/blog/2025/05/13/arrow-java-18.3.0/
Reacted by Raúl Cumplido- Reacted by Raúl CumplidoReacted by Gang Wu and Raúl CumplidoReacted by Gang Wu and Raúl Cumplido
- unpinned this issue
on Oct 8, 2025 - added a commit that references this issue
on Jan 12, 2026
Describe the enhancement requested