IMO, we could have the following categories:
1) Sandbox: crazy ideas or something that don't have consensus yet in the
community (You can do whatever you want here :-)
2) Trunk/contrib: experimental features that are not ready to be included in
the next release
a) If the code can be built, the module should be included in the main
build
b) if the code cannot be built, the module won't be included in the main
build
3) Trunk/modules: stable features that are ready for the next release
Developers can adjust things between 2.a and 2.b. We should promote things from
2 into 3 when the features are ready.
We should always try to ensure the features included in the build passing no
matter if they are from "contrib" (2.a) or "modules" (3). The default maven
build profile should include both "contrib" and "modules". The release profile
will exclude "contrib". When we cut a release, the "contrib" will be excluded
from the distro.
Mostly, I prefer to have a "SOFT" separation between the experimental and
ready-for-release features.
Sent from my iPhone
On Jun 30, 2010, at 10:47 AM, Simon Laws <[email protected]> wrote:
> 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
