ant elder wrote:
On Mon, Oct 4, 2010 at 9:24 PM, Luciano Resende <[email protected]> wrote:
On Mon, Oct 4, 2010 at 12:53 AM, ant elder <[email protected]> wrote:
Totally agree with that. We should be trying hard to make trunk as small,
quick and easy to build as possible so should put stuff thats deemed not
quite ready yet somewhere else. If something isn't ready to be released or
build by the Hudson nightly build why should everybody else in the world
who's trying to build Tuscany have to try to check it out, build it, and get
all the extra dependencies.
Well, I guess couple of the community members like the ability to
include these modules as part of their development environment (e.g.
ability to generate IDE files as source dependencies, and have an
option to build together with other modules). Downloading these extra
sources will not really cause side effects to other developers, unless
they have to build it as part of the main profile, and from my
previous post, I was kind suggesting that, as long as the things that
are being brought up are built somewhere (e.g. Hudson), I'm fine with
this...
The sandbox or contrib area outside of trunk
seem much more appropriate places to put not yet ready things.
Now you got me totally confused... I have seen multiple e-mails from
you asking people to develop in trunk [1], but now you are suggesting
we go do development out of trunk ? Could you please clarify ?
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
...ant
