In Tuscany there are no hurdles for getting new code into trunk. However it would be easier, come release time, if we knew which modules we're ready for release and which where not. Here "ready for release" is in the eye of the developer(s) building the module in question, i.e. there is no checklist or committee that determines it.
We do have a contrib directory [1] which I think (just my view) *currently* fits into the grand scheme of things in the following way: my sandbox - stuff I just want to work on contrib - stuff that I think could go into a release at some point but which isn't ready yet trunk - stuff which I think is ready to release I chatted with others about this and there were various opinions about how we can improve so starting this [DISCUSS] to see if we can come to some common understanding. [1] http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/contrib/ Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
