Sorry that I couldn't contribute as I was on business travel. Quick question: Should we consider automating most of those release-related sanity tests as e.g. done by Derek below?
Best, Michael On 06/17/2014 11:24 PM, Derek Dagit wrote: > +1 > > > - Verified sigs and sums for: > - binary zip > - binary tarball > - source zip > - source tarball > > - Checked out tag v0.9.2-incubating: > - build from source on OSX 10.9.3, Java 1.7.0_60 > - Confirmed unit tests pass > > - Deployed binary tarball on Linux RHEL6 equiv., Java 1.7.0_25: > - Launched daemons: > - dev-zookeeper > - nimbus > - supervisor > - ui > - logviewer > - Launched word_count: > - Verified messages were moving > - Confirmed logviewer logs > - Confirmed UI: > - Checked visualization—WOW, this is cool!, confirmed auto-refresh > - Confirmed Kill button >
