I went ahead and committed a couple of changes to trunk and branch-2 to fix
the MR CHANGES.txt mess. Alexandro, I believe there's a couple of jiras
where you were waiting for CHANGES.txt fixes before merging to branch-2.
Not sure about past discussions, but can we re-visit removing CHANGES.txt
in
Thanks for taking care of this Sid.
Agree that using jira fix versions would be easier as a way to generate the
changes. It would require some proper handling by the committer. For
example, if something is committed to trunk(3.0.0) and branch-2(2.0.5) it
would have fixedVersion 2.0.5, if later it
Sorry for the delay on this, I was waiting for a couple of blockers to be
resolved. I am planning on spinning this release today.
Tom
On 3/21/13 10:25 AM, "Thomas Graves" wrote:
>Thanks everyone for voting. With 4 binding +1, 4 non-binding +1, and no -1
>the release plan passes. I will make a
Hello Mohammad,
Which version of the codebase?
If it's trunk or branch-2, then for the datanode side, I recommend starting
from
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java.
Look for a method named sendHeartBeat. On the namenode side,
I've created a release candidate (RC0) for hadoop-0.23.7 that I would like
to release.
This release is a sustaining release with several important bug fixes in
it.
The RC is available at:
http://people.apache.org/~tgraves/hadoop-0.23.7-candidate-0/
The RC tag in svn is here:
http://svn.apache.org
Sid, I checked this into 2.0.4-alpha.
Thanks,
+Vinod
On Apr 9, 2013, at 11:14 PM, Siddharth Seth wrote:
> Arun, MAPREDUCE-5094 would be a useful jira to include in the 2.0.4-alpha
> release. It's not an absolute blocker since the values can be controlled
> explicitly by changing tests which use
Talked to Arun offline and merged this into 2.0.4-alpha. Also fixed CHANGES.txt.
Thanks,
+Vinod
On Apr 10, 2013, at 9:10 PM, Alejandro Abdelnur wrote:
> I've comitted HADOOP-9471 to trunk and branch-2 and closed JIRA with
> fixedVersion 2.0.5.
>
> If this JIRA makes it to 2.0.4 we need to upda