dybyte opened a new issue, #13047: URL: https://github.com/apache/seatunnel/issues/13047
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description ### Description `docs/{en,zh}/introduction/concepts/incompatible-changes.md` has only one `## dev` section. It has never been split per release. So: - The doc shipped in the `2.3.13` and `v3.0.0` tags lists everything under `## dev`, so the published 3.0.0 docs show "dev" instead of the version. - On `dev`, the 2.3.13 entries, the 3.0.0 entries and the changes made after 3.0.0 (e.g. the Java 11 baseline, `-i` variables, Redis auth) all sit together. Users upgrading from a given version can't tell which entries apply to them. ### Proposal Every PR adds its entry in the same change, so diffing the doc between release tags gives the split: - `## dev`: entries added in `v3.0.0..dev` - `## 3.0.0`: entries in the `v3.0.0` doc that are not in `2.3.13` - `## 2.3.13`: entries in the `2.3.13` doc Apply the same structure to `docs/en` and `docs/zh`. Optionally, add a release step that renames `## dev` to the version being released and opens a new `## dev` section. The doc was introduced in #10068. ### Usage Scenario _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
