>> >> I do say development should happen in trunk, thats a fundamental part >> of the Apache Way. I guess the point is that whats in trunk/contrib >> (now unreleased) is that its not being actively developed, most of its >> not been changed for months, its not included in any build, the >> pom.xmls are out of date so that it doesn't build, there is no doc, >> and there are no tests. Other than to the individuals who added the >> bits its just cruft that we're making everyone who checks out Tuscany >> download. Anyway, we've got trunk/unreleased now and as so many of you >> seem keen on it i guess that will stay but IMHO you should regularly >> consider why what you have put in there is there and either move it to >> contrib out of trunk or if its work to be continued move it to trunk >> proper. >> > In 1.x quite a few (but not all) of the unreleased modules are in the > build. I'm not sure what their status is in terms of tests and > documentation. > > I agree that things shouldn't stay in trunk/unreleased as a long-term state > of affairs. Its purpose should be as a staging post toward becoming part of > a release. > > I think the first step for 1.x should be to move the unreleased modules > and samples to trunk/unreleased and see what ends up there. The second step > would be to see whether anyone wants to put in the work to get these things > into a releasable state. If not, they can be moved out of trunk and > archived. > > Simon >
+1 Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
