> On Oct 23, 2015, at 7:56 PM, Sean Busbey <[email protected]> wrote:
>
> I would like to start leveraging Yetus in some other projects. I don't
> want to rush the current work on a sustainable build system for
> project wide use, so for now I'd like to just document how to hand
> assemble appropriate source and convenience binary artifacts.
I think that’s reasonable.
> I think it's clear we can offer value in our current state, even if
> working across components will awkward. We need to discuss versioning
> and release cadence, but I don't want to start those conversations
> unless we're prepared to start releasing.
The fact that Hadoop Common precommit moved in a net positive
direction during the current beta test is definitely a great sign that the
value is there. Plus, given that most of the remaining issues are
hadoop-specific, other projects will likely have a completely positive move.
> What do folks think? Are there at least 2 other PMC members ready to
> vote? Something in particular anyone would like to see implemented
> before we start having releases?
I’d probably want to see one big thing, one small thing:
- different directory structure. The hadoop-imported model of
everything in /dev-support is pretty terrible. We’d need to put people on
notice that it is likely going to change again though, esp when we do add a
build system, get unit tests, etc.
- publish more documentation
* shelldocs generated API info from test-patch
* javadoc from annotations
