+ I verified the md5 + release-log.txt no longer says "unreleased"
+ I ran the tests successfully + Built and started correctly against hadoop 1.1.1 + Submitted some of the example jobs, played with the web UI and CLI a bit +1 thanks - Robert On Thu, Jan 17, 2013 at 4:29 PM, Alejandro Abdelnur <[email protected]>wrote: > +1 > > verified MD5 and signature. > removed release-log.txt file from rc0 and rc1 and run "find . -type f | > sort | xargs -I % cat | md5" in both, got same MD5 in both (so build, > install, config, run checks apply) > > > On Thu, Jan 17, 2013 at 3:50 PM, Virag Kothari <[email protected]> > wrote: > > > Hi, > > > > The release candidate 1 for Oozie 3.3.1 is available. > > > > Oozie 3.3.1 has a critical bug fix related to upgrade of jobs from 3.2 to > > 3.3. In addition, it has several other improvements for stability and few > > bug fixes. > > Detail release log can be found at > > http://people.apache.org/~virag/oozie-3.3.1-rc1/release-log.txt< > > http://people.apache.org/~virag/oozie-3.3.1-rc0/release-log.txt> > > > > > > Keys to verify the signature of the release artifact are available at > > > > http://www.apache.org/dist/oozie/KEYS > > > > > > Please download, test, and try it out: > > > > http://people.apache.org/~virag/oozie-3.3.1-rc1/< > > http://people.apache.org/~virag/oozie-3.3.1-rc0/> > > > > > > The release, md5 signature, gpg signature, and rat report can all > > be found at the above address. > > > > > > Vote closes after 3 days from now. (Jan 20 16:00 PST) > > > > > > Thanks, > > > > Virag > > > > > > -- > Alejandro >
