Yicong-Huang commented on code in PR #58288:
URL: https://github.com/apache/spark/pull/58288#discussion_r3875640855
##########
dev/merge_spark_pr.py:
##########
@@ -1179,6 +1285,56 @@ def reconcile_jira_components(issue, title_components):
jira_ops.update_components(issue, new_names)
+def reconcile_jira_affects_versions(issue, fix_version_names,
affects_available):
+ """Prompt the committer to update the JIRA Affects Version/s during a
merge.
+
+ Meant for the case the caller gates on with ``fix_precedes_affects``: the
affected
+ floor sits above the earliest fix, so a fixed release is not admitted as
affected.
+ Mirrors the Fix Version prompt but targets ``issue.fields.versions``: it
shows the
+ current Affects Version/s and the fix version(s) being set, offers a
default
+ inferred from the fix version(s) via ``suggest_affects_versions``, then
reads a
+ comma-separated entry validated against ``affects_available`` (all
unarchived
+ versions, since an affected version may be released) with a retry loop. A
blank
+ entry accepts the suggested default; otherwise the parsed versions replace
the
+ current ones (through ``jira_ops`` so a dry run only logs the intended
write).
+ """
Review Comment:
thanks for the suggestion, rewrote this part and just stating the invariant
(affects Version/s should reach down to the earliest fixed release).
For Jira, I left it as JIRA to match the rest of file, we could update them
(and all other places together) later.
--
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]
