RE: trunk or 3.3 ?

 

> -----Original Message-----
> From: news [mailto:[email protected]] On Behalf Of Jorg Heymans
> Sent: 05 August 2004 14:13
> To: [email protected]
> Subject: trunk or 3.3 ?
> 
> Hi,
> 
> I'm new to Merlin but not new to some of its concepts (have 
> been using cocoon intensively the last 18 months)
> 
> I would like to use Merlin because
> a) it fits nicely with the things i learned while developing 
> with cocoon
> b) i think it would make a killer backend for any system that 
> has cocoon servicing the view, pulling its data from 
> merlin/avalon components.
> 
> Now, having read through the posts of the lasts couple of 
> weeks I am a bit confused: is the 3.3 distro a good start to 
> learn more or should i checkout the trunk as suggested in 
> thread "Where to begin" a few weeks ago?

The suggestion from a few weeks ago was linked to an interest in the Magic
build system as well as Merlin.  The 3.3. distribution is good and solid
whereas 3.4 (trunk) is the center of development attention and all major
subsystem implementations (meta, composition, activation) are in SNAPSHOT
status.

> Secondly, is there a list of live-sites/products built with Merlin?

Not that I know off. Over the last six months there have been several
evaluation projects and personally aware of a number of current product
iniatives based on 3.3.0 (and at least two working against 3.4.0).

> Thirdly, how mature is Merlin? Can it be used in its current 
> state as the basis for a long-term project? How much of it is 
> in flux and how much of it will be changing (user-visible) in 
> the near future?
> 
> 
> Sorry for these questions, just playing the "suspicious new customer" 
> role here ;)

You question concerning suitability does depend on the intended usage of the
Merlin platform.  There are two distinct usage patterns - firstly, as a
standalone service management platform, and secondly, as an embedded
solution.  In the first scenario - the content that the user is exposed to
(configuration files and so on) has been really stable for a long time now
and merlin does not add anything outside of the Avalon Framework contract.
If your considering container customization (which is getting in some rather
advanced stuff) then working against trunk may be desirable.

Cheers, Steve.

> 
> Thanks!
> Jorg Heymans
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>