wombatu-kun opened a new pull request, #16544:
URL: https://github.com/apache/iceberg/pull/16544

   Closes #15191
   
   ## Summary
   
   Apache Iceberg publishes a nightly snapshot of every module to the Apache 
snapshot repository (via the `publish-snapshot` workflow, daily at 00:00 UTC), 
but until now this was only mentioned in a single sentence in 
`multi-engine-support.md` with no usage examples. This PR adds a dedicated, 
developer-only page documenting how to consume those snapshots, addressing 
https://github.com/apache/iceberg/issues/15191.
   
   Per the ASF [release policy on 
publication](https://apache.org/legal/release-policy#publication) — and the 
point raised in the issue discussion — the page leads with a prominent warning 
that snapshots are unreleased, must not be used in production, and are intended 
only for active Iceberg developers, directing everyone else to official 
releases.
   
   ## What changed
   
   - New `site/docs/nightly-snapshots.md`: a "developers only" warning 
admonition, an explanation of the daily snapshot and its version, and 
copy-pasteable Gradle, Maven, sbt, and Spark examples that add the snapshot 
repository and depend on the snapshot version.
   - `site/mkdocs.yml`: a new `snapshotVersion` macro (`1.12.0-SNAPSHOT`) so 
the version in the examples stays current the same way `icebergVersion` does; 
the Spark example also reuses the existing `sparkVersionMajor` macro.
   - `site/nav.yml`: adds the page under the developer-facing "Project" section 
(not top-level "Releases"), reinforcing that snapshots are for developers.
   - `site/docs/multi-engine-support.md`: re-points the existing one-line 
snapshot mention to the new page instead of duplicating it.
   - `site/docs/how-to-release.md`: notes that the "Site update" release step 
should also bump `snapshotVersion`, so the macro does not go stale.


-- 
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]

Reply via email to