keksmd commented on issue #979: URL: https://github.com/apache/incubator-graphar/issues/979#issuecomment-5816204043
@SemyonSinchenko could you sanity-check my understanding of how the Java SDK gets to Maven Central, and tell me where I'm wrong? What I found: no `org.apache.graphar` artifact exists on Maven Central or in the ASF snapshot repository today; v0.13.0 shipped as a source release only. How I understand the path: 1. **Build side**: #980 makes the SDK POMs resolvable outside the reactor (flattened, no unpublished parent), adds SCM/developer metadata and the incubator DISCLAIMER to the jars, and adds a snapshot workflow for `repository.apache.org`. 2. **INFRA**: a PPMC member files an INFRA Jira ticket to configure the `org.apache.graphar` groupId in the ASF Nexus (staging + snapshots) and to provision the `NEXUS_USER` / `NEXUS_PW` secrets on this repository. Until that happens the snapshot deploy fails with 401. 3. **Release**: the release manager stages the Maven artifacts in Nexus alongside the source tarball, then the usual dev@ vote, then the IPMC vote, then the staging repository is promoted to Central. Questions: - Is this right, or does GraphAr prefer a different route (for example, Maven artifacts only in a later release, or a separate Java release train)? - Could you file the INFRA ticket, or tell me who on the PPMC should? I'm happy to draft its text. - Who would act as release manager for the next release with Java artifacts? @yangxk1 ran v0.13.0; would publishing the Maven artifacts fit into the next release? - The Java version is still `0.13.0-SNAPSHOT` after 0.13.0 shipped. Should #980 bump it to `0.14.0-SNAPSHOT`, or should that be left to the release manager? For context, the first useful release for Java users would include the Parquet backend (#975), the reader (#978), and the writer (#973). This is what lets applications drop the FastFFI/JNI binding. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
