pan3793 opened a new pull request, #3818: URL: https://github.com/apache/celeborn/pull/3818
### What changes were proposed in this pull request? When resolving a JIRA after merging a PR, the suggested fix version for `main` was the first unreleased version returned by the JIRA API, which is ordered by creation time rather than version number. As a result, `main` could suggest an old unreleased version (e.g. `0.3.3`) instead of the next main release (e.g. `1.0.0`). This PR follows the version inference approach of SPARK-56865 in `dev/merge_spark_pr.py`: suggested fix versions are picked by semantic version, with `main` contributing the greatest unreleased `N.0.0` and `branch-M.N` contributing the greatest unreleased `M.N.x`. It also requires JIRA version names to be exactly `x.y.z`, excluding malformed entries such as the current `0.5.2, 0.4.3, 0.6.0`. ### Why are the changes needed? The default suggestion was wrong for PRs merged to `main`, requiring committers to correct it manually. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? `python3 -m py_compile dev/merge_pr.py`, plus manual checks of `compute_default_fix_versions` against the current unreleased CELEBORN versions: `main + branch-0.7` now suggests `1.0.0,0.7.1` instead of `0.3.3,0.7.1`. Assisted-by: deepseek-v4-pro -- 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]
