[
https://issues.apache.org/jira/browse/HADOOP-14356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated HADOOP-14356:
------------------------------------------
Attachment: HADOOP-14356-branch-2.7-003.patch
[~ajisakaa] thanks for review.. Updated the patch.
[~shv] thanks for looking into this issue.
bq. May be we should keep it open in case other inconsistencies with
CHANGES.txt emerge. Make it the last commit before the release?
As of now, can we commit with this current missed list and track the commits
till the release(which I used to do,then there I will try to update,so that
every committer will be knowing)?
Or
will wait till release,as you mentioned..?
anything is ok for me.
> Update CHANGES.txt to reflect all the changes in branch-2.7
> -----------------------------------------------------------
>
> Key: HADOOP-14356
> URL: https://issues.apache.org/jira/browse/HADOOP-14356
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Priority: Blocker
> Labels: release-blocker
> Attachments: HADOOP-14356-002.patch,
> HADOOP-14356-branch-2.7-003.patch, HADOOP-14356.patch
>
>
> Following jira's are not updated in {{CHANGES.txt}}
> HADOOP-14066,HDFS-11608,HADOOP-14293,HDFS-11628,YARN-6274,YARN-6152,HADOOP-13119,HDFS-10733,HADOOP-13958,HDFS-11280,YARN-6024
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
