Thanks for checking it.
I think it's fine by two reasons below:
1. It has another condition for such cases - one year time range.
Basically, such PRs have not been merged for one year, which I believe are not likely merged soon.
The JIRA status will be updated when such PRs are merged anyway.
2. The JIRAs and PRs ideally should be updated. If the PR authors forgot to update affected versions,
it could be a good ping to update the affected versions in its JIRA, which is a good practice I believe.
FWIW, currently setting 'in-Progress' doesn't properly work. It has been few months.
I raised this issue several times at http://apache-spark-developers-list.1001551.n3.nabble.com/In-Apache-Spark-JIRA-spark-dev-github-jira-sync-py-not-running-properly-td27077.html
it blocked me to search JIRAs. I had to change my JQL to check JIRAs. It's still not being fixed. I don't know who to ask about this.
If this is not being fixed, we might not have to care about 'In-Progress' anymore.
I checked entries in the list and I found that some entries have 'In-Progress' in their status and have oepn prs (e.g., SPARK-25211
We can also close these PRs according to the bulk close?
(But, we might need to check the corresponding PRs manually?)
We have resolved JIRAs that targets EOL releases (up to Spark 2.2.x) in order to make it
the manageable size before.
Since Spark 2.3.4 will be EOL release, I plan to do this again roughly in a week.
The JIRAs that has not been updated for the last year, and having affect version of EOL releases will be:
- Resolved as 'Incomplete' status