[
https://issues.apache.org/jira/browse/SPARK-48904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kent Yao updated SPARK-48904:
-----------------------------
Affects Version/s: 4.1.0
> Update doc's version field to align with fixedVersion field of JIRA ticket
> --------------------------------------------------------------------------
>
> Key: SPARK-48904
> URL: https://issues.apache.org/jira/browse/SPARK-48904
> Project: Spark
> Issue Type: Umbrella
> Components: Documentation, Spark Core, SQL
> Affects Versions: 4.1.0, 4.0.0
> Reporter: Kent Yao
> Priority: Major
>
> When a PR merged into more than 2 branches and if it contains version
> information, for example:
> - since tag for scala/java API
> - versionadded directive for python APIs
> - .version(..) method for configurations
> - Since Versions in documentation
> - Since annotation in expression information
> - e.t.c
> we currently add the smallest version to the code. Take 3.4.4, 3.5.2, 4.0.0
> for an example, it logs as fixed/since 3.4.4, it's easy for users who stay in
> 3.4.x and upgrade to 4.x but hard for those who use 3.5.x to know whether it
> gets fixed or not.
> So, I suggest we make these fields more informative which means logging
> '3.4.4, 3.5.2, 4.0.0' together, which also aligns with the JIRA ticket "Fix
> Version/s:" field.
> See:
> https://github.com/apache/spark/commit/d8820a07eb82acd35a1c9d4ff6ee4f65fc6aac29
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
