saihemanth-cloudera commented on code in PR #120: URL: https://github.com/apache/hive-site/pull/120#discussion_r4066706094
########## content/community/resources/howtorelease.md: ########## @@ -528,6 +534,49 @@ Regards, The Apache Hive Team ``` +### Verify Maven Central artifacts + +After Nexus release (and again before the `[ANNOUNCE]` mail), confirm that Maven Central has the modules users expect. Maintenance releases should publish the same `org.apache.hive` modules as the previous GA in that line (handlers, Iceberg, JDBC, and so on). + +Download and run the checker script from this repository (or copy it from your `hive-site` clone): + +``` +curl -O https://hive.apache.org/scripts/verify-maven-central-release.sh +chmod +x verify-maven-central-release.sh +./verify-maven-central-release.sh 4.2.0 4.2.1 +``` + +Replace versions with the previous GA and the release you just shipped. The script discovers `org.apache.hive` artifacts from Maven Search for the previous version and checks that each **JAR** artifact is also published for the new version (POM-only aggregator modules are skipped). It exits with a non-zero status if anything is missing. + +You can also run it from a local `hive-site` checkout: + +``` +./static/scripts/verify-maven-central-release.sh <previous-version> <new-version> +``` + +Include a note in the RC vote thread that voters may run this check after artifacts are staged. Review Comment: Ack ########## content/community/resources/howtorelease.md: ########## @@ -528,6 +534,49 @@ Regards, The Apache Hive Team ``` +### Verify Maven Central artifacts + +After Nexus release (and again before the `[ANNOUNCE]` mail), confirm that Maven Central has the modules users expect. Maintenance releases should publish the same `org.apache.hive` modules as the previous GA in that line (handlers, Iceberg, JDBC, and so on). + +Download and run the checker script from this repository (or copy it from your `hive-site` clone): + +``` +curl -O https://hive.apache.org/scripts/verify-maven-central-release.sh +chmod +x verify-maven-central-release.sh +./verify-maven-central-release.sh 4.2.0 4.2.1 +``` + +Replace versions with the previous GA and the release you just shipped. The script discovers `org.apache.hive` artifacts from Maven Search for the previous version and checks that each **JAR** artifact is also published for the new version (POM-only aggregator modules are skipped). It exits with a non-zero status if anything is missing. + +You can also run it from a local `hive-site` checkout: + +``` +./static/scripts/verify-maven-central-release.sh <previous-version> <new-version> +``` + +Include a note in the RC vote thread that voters may run this check after artifacts are staged. + +### Republishing missing Maven modules + +If verification finds gaps (as in [HIVE-30010](https://issues.apache.org/jira/browse/HIVE-30010)): + +1. Check out the release tag, for example `rel/release-X.Y.Z`. +2. Identify modules published for the previous GA but missing for the new version (the script above, or compare Central manually). +3. Build only the missing modules: `mvn install -pl <module-list> -am -DskipTests`. **Iceberg modules require `-PerrorProne`** (Immutables annotation processing in `iceberg/pom.xml`). +4. Deploy only those modules: `mvn deploy -pl <module-list> -Papache-release -DskipTests -Dmaven.javadoc.skip=true` (do not use `-am` on deploy, to avoid republishing artifacts already on Central). +5. Close and release the new staging repository in Nexus, then re-run the verification script. + +Keep release helper scripts **outside** the `hive` source tree (for example next to your clone). Scripts in the Hive repo root without Apache license headers will fail `mvn apache-rat:check`. + +### Release notes for website updates + +When updating `hive-site` for a new version, remember: + +* `content/general/downloads.md` — news entry and JIRA changelog link (look up the Fix Version id in JIRA). +* `content/docs/javadocs.md` — link to `/javadocs/rX.Y.Z/api/index.html` on the ASF javadoc SVN path. +* `config.toml` — `[params.release].version` and the `announcements` anchor under `[params.navbar]`. +* `themes/hive/layouts/partials/release-banner.html` — homepage “new release” banner text (easy to forget after `downloads.md` is updated). + Review Comment: Ack. -- 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]
