[
https://issues.apache.org/jira/browse/HADOOP-11792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179610#comment-15179610
]
Marco Zühlke commented on HADOOP-11792:
---------------------------------------
With this change we are relying on the correctness of the JIRA fixVersion
field.I think this is the right move.
The [wiki|https://wiki.apache.org/hadoop/HowToCommit] has the following guide:
bq. Always set the "Fix Version" at this point, but please only set a single
fix version, the earliest release in which the change will appear. Special
case- when committing to a non-mainline branch (such as branch-0.22 or
branch-0.23 ATM), please set fix-version to either 2.x.x or 3.x.x appropriately
too.
I my eyes this would (currently) for most issues mean:
* exactly one of "3.0.0", "2.9.0" or "2.8.0"
* in addition for backports to branch-2.7 add "2.7.3"
* in addition for backports to branch-2.6 add "2.6.5"
Exceptions are issues are are only relevant for a specific branch.
But when browsing over all fixed JIRAs you see wide variety:
https://issues.apache.org/jira/issues/?jql=project%20in%20%28YARN%2C%20HADOOP%2C%20HDFS%2C%20MAPREDUCE%29%20AND%20%20%20fixVersion%20in%283.0.0%2C2.9.0%2C2.8.0%2C2.7.0%2C2.7.1%2C2.7.2%2C2.7.3%2C2.6.0%2C2.6.1%2C2.6.2%2C2.6.3%2C2.6.4%2C2.6.5%29%20%20ORDER%20BY%20updated%20DESC
To just pick some:
* YARN-4344: 2.7.2, 2.6.3
* HDFS-9855: 2.8.0, 2.9.0
* HADOOP-12841: 3.0.0, 2.9.0
* YARN-4722: 2.8.0, 2.7.3, 2.9.0, 2.6.5
* ...
> Remove all of the CHANGES.txt files
> -----------------------------------
>
> Key: HADOOP-11792
> URL: https://issues.apache.org/jira/browse/HADOOP-11792
> Project: Hadoop Common
> Issue Type: Task
> Components: build
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Andrew Wang
> Fix For: 2.8.0
>
>
> With the commit of HADOOP-11731, the CHANGES.txt files are now EOLed. We
> should remove them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
