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

   ## Which issue does this PR close?
   
   N/A. Release chore for 1.1.0.
   
   ## Rationale for this change
   
   1.1.0 is published (tag `1.1.0`). This publishes the 1.1.0 user guide and 
makes it the default (current stable) version in the documentation, following 
the "Publishing Documentation" step of the [release 
process](https://github.com/apache/datafusion-comet/blob/main/docs/source/contributor-guide/release_process.md).
 It repeats the pattern from #5290 (1.0.0) and #4698 (0.17.0).
   
   ## What changes are included in this PR?
   
   - `docs/generate-versions.py`: `latest_released_version = "1.1.0"`, and 
`1.0.0` moves into `previous_versions` (older guides are kept).
   - `docs/build.sh`: clean up the locally cloned `comet-1.1` branch dir before 
regenerating.
   - `docs/source/user-guide/index.md`: current stable release is now 1.1.x, 
and the sidebar entry points at `1.1/index`.
   - `docs/source/user-guide/older-versions.md`: point the "current stable 
release" link at 1.1 and add 1.0.x to the list.
   
   Not included (separate follow-up per the release process): bringing 
`docs/source/changelog/1.1.0.md` into `main`, if it is not already there.
   
   ## How are these changes tested?
   
   Ran `docs/generate-versions.py` against a copy of `docs/source`. It cloned 
`branch-1.1` and produced `user-guide/1.1` with `$COMET_VERSION` replaced by 
`1.1.0`. A Sphinx HTML build of that tree adds no warnings for the touched 
pages. `user-guide/index.html` shows "1.1.x (current)" and the 1.0.x entry, and 
both `1.1/index.html` and `1.0/index.html` render. I did not run the full 
`docs/build.sh`, which also runs Maven per Spark profile to generate the dev 
snapshot pages. The documentation CI workflow covers that.


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