> On Dec 12, 2015, at 11:31 AM, Allen Wittenauer <[email protected]> wrote: > > >> On Dec 11, 2015, at 9:56 AM, Sean Busbey <[email protected]> wrote: >> >> Please take a few minutes to verify the release[1] and vote on releasing it: >> >> [ ] +1 Release this package as Apache Yetus 0.1.0 >> [ ] +0 no opinion >> [ ] -1 Do not release this package because... > > > At the moment, I’m +0. > > I’ve switched HADOOP, HDFS, and YARN over to use bin/test-patch from the RC > tar ball via DL’s from > https://dist.apache.org/repos/dist/dev/yetus/0.1.0-RC1/. I’ve had *one* > instance where things went haywire
24 hours later and I’m not seeing the problem anymore. This includes running the same patch on the same Jenkins slave under what I believe to be the same conditions. So I’m inclined to believe it was either a temporary glitch, an edge case that’s going to be extremely hard to reproduce, or maybe someone doing something in the background invisible to us. So after running from git master for a week+, using the binary tarball for over 24 hours, verifying the keys, etc, my vote is now… +1 (binding)
