+1 (binding) - Verified md5, signature, release log and rat report - Ran the unit tests and they are all good. There was one known flaky test which was fine on rerun. - Executed a simple workflow
Regards, Rohini On Wed, Jan 17, 2018 at 5:57 AM, Attila Sasvari <asasv...@cloudera.com> wrote: > Many thanks Satish. > > +1 (non-binding) > > Testing done: > - Verified md5 and signature, release-log.txt is up to date > - Created distro with the mkdistro script using -Puber -Phadoop-2 > -Dhadoop.version-2.6.0 > - Executed example workflows (all except Hive related ones) / coordinators > / bundles on a pseudo Hadoop 2.6.0 - each succeeded > - Submitted Spark example workflow no only in local mode, but also on YARN > (master=yarn, mode=client/cluster) > - Tested FS action > - Clicked through the Web UI. Job logs can be retrieved, DAG is displayed, > version is correct > > > > On Wed, Jan 17, 2018 at 6:18 AM, satish saley <satishsa...@apache.org> > wrote: > > > Hi, > > I have created a build for Oozie 4.3.1, candidate 1. > > It includes all the changes decided earlier except OOZIE-3018 and > > OOZIE-3072. OOZIE-3018 makes changes to SchemaCheckerService which we are > > not picking. OOZIE-3072 makes changes to files created in OOZIE-1770. > > 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/~satishsaley/oozie-4.3.1-rc1 > > The release, md5 signature, gpg signature, and rat report can allbe found > > at the above address. > > Vote closes on 01/19/2018 11:59 PM PT. > > -Satish Saley > > > > > -- > -- > Attila Sasvari > Software Engineer > <http://www.cloudera.com/> >
