rmoff commented on issue #12917: URL: https://github.com/apache/iceberg/issues/12917#issuecomment-3052840457
I agree that _both_ `latest` and `1.9.1` becomes confusing (is 1.9.1 not the latest?) and takes up more nav space. Before we fix it thought, a couple of thoughts: ## Navigation Do we even need the term `latest`? Or we show the latest version (e.g. `1.9.1`) as current and people can take from that that it's the latest version? ## Permalinks Ideally someone linking to the current version of the docs should not be baking in a link that's then hardcoded to a version which ages and thus their link ages. *Unless* they are deliberately wanting to link to a specific version's docs. But this feels like something that's contrary to the principle of hyperlinks in general, so I discount it. --- For reference, Apache Kafka has their docs link `https://kafka.apache.org/documentation/` serving docs for the latest version, and just lists the version number in the heading; there's no `latest` terminology. <img width="2240" height="1252" alt="Image" src="https://github.com/user-attachments/assets/dc4c8dfe-a104-427b-a687-f6b4a8931388"; /> Apache Flink does the same `https://nightlies.apache.org/flink/flink-docs-stable/` <img width="2394" height="530" alt="Image" src="https://github.com/user-attachments/assets/88573a30-3b83-47a2-b041-bef3479af8a2"; /> -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
