[
https://issues.apache.org/jira/browse/HDFS-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201168#comment-13201168
]
Harsh J commented on HDFS-2898:
-------------------------------
I looked deeper at this, just among the diffs of the 0.23.1 sections and here
are the discrepancies:
||JIRA||Listed on Trunk's 0.23?||Listed on Real 0.23?||Committed to 0.23?||
|HDFS-208|Yes|No|No|
|HDFS-2294|Yes|No|Yes, but in .0|
|HDFS-2322|Yes|No|Yes, but in .0|
|HDFS-2614|No|Yes|Yes|
|HDFS-2705|No|Yes|Yes|
|HDFS-2784|No|Yes|Yes|
|HDFS-2785|No|Yes|Yes|
|HDFS-2814|No|Yes|Yes|
|HDFS-2857|Yes|No|Not yet, looks like author ran into merge issue as described|
> branch-0.23 and trunk CHANGES.txt sections are out of sync
> ----------------------------------------------------------
>
> Key: HDFS-2898
> URL: https://issues.apache.org/jira/browse/HDFS-2898
> Project: Hadoop HDFS
> Issue Type: Task
> Components: documentation
> Affects Versions: 0.23.1
> Reporter: Harsh J
>
> While committing HDFS-2868, merging (backporting) didn't turn out to be super
> easy since the CHANGES.txt section for IMPROVEMENTS under 0.23.1 have
> diverged between trunk and branch-0.23.
> We should get it back in sync to have easier backports than having to
> manually resolve CHANGES.txt. Should we source the list from trunk?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
