On Oct 15, 2015, at 8:50 PM, Sean Busbey <[email protected]> wrote: > if there's going to be more than one experimental downstream, I'd > prefer we start voting on release artifacts (say, a tarball of our > source checkout) so that we can get a release cadence going. I'd be > fine with doing this while e.g. Hadoop's adoption is being driven in a > branch. > > For getting Hadoop working this weekend, I think a working > commit-without-review branch is reasonable. I'd like there to be a > yetus jira that tracks the branch's lifecycle, with the branch named > for it.
I’ve opened YETUS-83 and created said branch. Thanks!
