Doug Cutting wrote:
Patrick Hunt wrote:
my original intent was to have it as zookeeper/trunk/src/contrib/... where this directory will have not only recipes but also other contributions.

+1 That's what I meant too. And since you've said you want to package these all as a single jar, then there should just be a single tree per language, right?

Yes, that's right.

zookeeper/trunk/src/contrib/recipes/src/java/org/apache/zookeeper/recipes/locking/ zookeeper/trunk/src/contrib/recipes/src/c++/locking/


I don't see the strong connection between releases and new features.
Am I missing something?

I think that the issue is implied connotation of "contrib".

We were thinking of contrib as "interesting stuff that users might want to re-use/share but not core to zookeeper, we'll carry it around so that users know where to find it, if it gets broken and no one fixes it it won't hold up the release"

If I understand correctly you are saying there is no middle ground.


Reply via email to