andygrove opened a new pull request, #7454:
URL: https://github.com/apache/datafusion-comet/pull/7454

   ## Which issue does this PR close?
   
   N/A. Release chore for 1.2.0.
   
   ## Rationale for this change
   
   1.2.0 is published (tag `1.2.0`). This PR publishes the 1.2.0 user guide and 
makes it the current stable version in the documentation. It follows the 
"Publishing Documentation" step of the [release 
process](https://github.com/apache/datafusion-comet/blob/main/docs/source/contributor-guide/release_process.md)
 and repeats the pattern from #6736 (1.1.0) and #5290 (1.0.0).
   
   ## What changes are included in this PR?
   
   - `docs/generate-versions.py`: `latest_released_version = "1.2.0"`, and 
`1.1.0` moves into `previous_versions`. Older guides are kept.
   - `docs/build.sh`: delete the locally cloned `comet-1.2` branch dir before 
regenerating.
   - `docs/source/user-guide/index.md`: the current stable release is now 
1.2.x, and the sidebar entry points at `1.2/index`.
   - `docs/source/user-guide/older-versions.md`: point the "current stable 
release" link at 1.2 and add 1.1.x to the list.
   
   The 1.2.0 change log is already on `main` 
(`docs/source/changelog/1.2.0.md`), so this PR doesn't add it.
   
   ## How are these changes tested?
   
   I ran `docs/generate-versions.py` against a copy of `docs/source`. It cloned 
`branch-1.2` and produced `user-guide/1.2`, with `$COMET_VERSION` replaced by 
`1.2.0` (the installation page links the 1.2.0 jars). The 1.1 pages now carry 
the out-of-date warning and the 1.2 pages don't. I didn't run a local Sphinx 
build or the full `docs/build.sh`, which also runs Maven per Spark profile to 
generate the dev snapshot pages. The documentation CI workflow covers both.
   


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