You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Szehon Ho (Jira)" <ji...@apache.org> on 2026/09/29 23:50:00 UTC

[jira] [Resolved] (SPARK-59808) Remove JIRA fix versions when merging reverts

     [ https://issues.apache.org/jira/browse/SPARK-59808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Szehon Ho resolved SPARK-59808.
-------------------------------
    Fix Version/s: 5.0.0
       Resolution: Fixed

Issue resolved by pull request 59082
[https://github.com/apache/spark/pull/59082]

> Remove JIRA fix versions when merging reverts
> ---------------------------------------------
>
>                 Key: SPARK-59808
>                 URL: https://issues.apache.org/jira/browse/SPARK-59808
>             Project: Spark
>          Issue Type: Bug
>          Components: Project Infra
>    Affects Versions: 5.0.0
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 5.0.0
>
>
> The merge script recognizes revert PR titles but still routes their JIRA updates through the resolve/add flow. Fix versions can therefore remain on a ticket after the associated change has been reverted.
> Spark release issue lists use JIRA fix versions. These stale entries can cause release notes to list changes absent from the release and require manual cleanup by release managers.
> When merging or backporting a revert, offer to remove recorded, unreleased fix versions inferred from the branches receiving the revert. Allow the committer to edit, skip, and confirm the selection, preserve other versions and ticket status, and support dry runs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org