Leo Simons wrote:
On Fri, 2002-11-15 at 08:48, Stephen McConnell wrote:Totally agree on the ECM point - however - I concerned about the very high learning curve the Phoenix represents in terms of an entry point. Ok - on Fortress and Merlin there isn't a trealease status for good reasons. On Tweety I think the scenario is different bacause I don't think Tweety should be released - it should be part of the getting started with Avalon walk though. I.e. is about eduction and delivering concrete examples. Does the publication of good informative and eductional content require that we go through a product release procedure? Surely not.
Maybe it would be a good idea to include in this document some links to some of the other Avalon containers. The current content suggests Phoenix as a starting point which is a little like learning to swim at the deep end of the pool. It could be interesting to reference Tweety and the entry point, followed by Merlin and Fortress dealing with cause grained components, and wrapping up Phoenix at the application level.I don't really like it. I feel our documentation should point to
Thoughts?
released and easily downloadable software; atm, the only containers with
that status are phoenix and ECM, and I feel it is a good idea to not
stimulate usage of ECM.
I'm in favour of making things understandable based on useful examples and demonstrations.
Cheers, Steve.
When fortress,tweety etc are released it's a different thing
alltogether.
cheers,
- Leo
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@;osm.net http://www.osm.net -- To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
