I'd check against the svn tag which corresponds to the release...
I'm traveling right now, let get back in a bit.
Sent from my iPhone
On Jan 10, 2012, at 9:55 PM, Eli Collins <[EMAIL PROTECTED]> wrote:
> Hey Arun,
> Was looking at the 23.0 release bits and noticed that the contents of
> branch-23.0 and jira don't jive with the rc2 tarball that was released
> and put on the site. Jira and branch-23.0 indicate the 7 changes
> (below) are part of 23.0, but the tarball doesn't contain them, it
> stops at hash d4fee83 but includes the final version update to 0.23.0
> (or maybe that was done via mvn?). Does svn rev 1196995 correspond to
> what was released as 23.0?
> I'll update the jiras to reflect that they didn't make 23.0.
> * 380245f (branch-0.23.0) Changing branch-0.23.0 to 0.23.0.
> * 6a8c7e1 MAPREDUCE-3392. Fixed Cluster's getDelegationToken's API to return nul
> * edc2165 svn merge -c 1200734 from 0.23 for HDFS-2539.
> * 33617ae svn merge -c 1199403 from 0.23 for HDFS-2540.
> * 31416a5 svn merge -c 1198905 from 0.23 for HDFS-2528.
> * 8d94b63 svn merge -c 1197335 from 0.23 for HDFS-2527.
> * 14ea355 svn merge -c 1196812 from 0.23 for HADOOP-7792 and HDFS-2416.
> * ca3b3ac MAPREDUCE-3291. App fail to launch due to delegation token not found i
> * d4fee83 Setting version 0.23.0
> Btw got the tarballs from here: