I mean the docs are sort of part of the release so I'm hesistant to update a released artifact, I think we could reasonably call it a bug fix for 4.2.1?
On Thu, Jul 16, 2026 at 11:16 AM L. C. Hsieh <[email protected]> wrote: > Hi all, > > I'd like to check with the community on backporting a docs-only change to > the 4.2 line and regenerating the published documentation. > > SPARK-57234 (PR #56314) added a documentation page for Real-time Mode to > the Structured Streaming guide. It touches only two files under docs/ and > contains no code changes. I merged it to master and branch-4.x after the > 4.2 RC had been cut, following the convention that non-bug-fix changes go > to master/branch-4.x only once an RC exists, and I noted this on the PR at > merge time. > > Now that 4.2.0 is released, the author pointed out that the published 4.2 > documentation has no link to the Real-time Mode page. They asked whether we > could still add it. > > My proposal is to backport the PR to branch-4.2 and re-run the > docs-generation/publishing step of the release process so the 4.2 > documentation site picks up the page. Since this only republishes > documentation and does not require a new release artifact, I believe the > impact is low, but I wanted to confirm this is acceptable before proceeding. > > Does anyone see a problem with this, or is there a preferred way to update > already-published release docs? > > Thanks, > Liang-Chi > > -- Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/ <https://www.fighthealthinsurance.com/?q=hk_email> Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> YouTube Live Streams: https://www.youtube.com/user/holdenkarau Pronouns: she/her
