You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Alexis Agahi <al...@users.sf.net> on 2003/09/04 09:14:28 UTC

My feedback on Merlin & how about having a release?

Folks,

I've just finished the portage of OpenIM http://open-im.net (Jabber Server) 
using Merlin component manager.
OpenIM+Merlin seems now to be working pretty well: server still up after one 
week of stress tests.

My opinion on using Merlin is positive. Component composition and 
configuration is easy and powerfull. Block declaration is as simple as 
powerfull. Project integration is easy when you understand some stuffs, but 
to be honnest, Merlin documentation and tutorial are really helpfull. As I 
wrote before, and considering my (small) experience of Phoenix & Forteress, 
I've the feeling that Merlin stands perfectly beeteen these 2 compoment 
managers.

Now to help me to perform an official stable 1.1 OpenIM release, it should be 
really nice if Merlin team could settle a stable binary release.


Cheers

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: My feedback on Merlin & how about having a release?

Posted by Stephen McConnell <mc...@apache.org>.

Leo Simons wrote:

> Stephen McConnell wrote:
>
>> A while ago I posted this proposed roadmap.
>>
>> http://marc.theaimsgroup.com/?l=avalon-users&m=106070797526891&w=2
>>
>> No objections were raised - so I figure that its time to launch a 
>> release vote.
>
>
> On that roadmap:
>
> ! 1.1. evolution of the platform to provide equivalent
> !      functionality together with migration tools supporting
> !      Phoenix and Fortress user migration
>
> I thought that meant a primary part of the release plan was support 
> for phoenix and fortress, either through some compat layer and/or tools?
>
> Is that finished? Where is it? 


If it was complete it would not be on the roadmap. I expect this to 
evolve based on feedback reflecting real needs - some of which is 
already happening on the Phoenix side with several projects moving into 
migration.  I think Aaron is doing something of the dynamic compoents 
discovery side that plays into this and I've been digging into the JMX 
side over the last few days.  Also, a lot of minor updates over the last 
week have been addressing needs raised in these areas.

Remomber that the community vote on a roadmap - the PMC votes on 
distribution.  All I'm talking about here is voting on the roadmap.  
With that established the PMC can tick off publication of binary drops 
as they are produced on a rolling basis.

Steve.

>
>
> cheers!
>
> - LSD
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: My feedback on Merlin & how about having a release?

Posted by Leo Simons <le...@apache.org>.
Stephen McConnell wrote:
> A while ago I posted this proposed roadmap.
> 
> http://marc.theaimsgroup.com/?l=avalon-users&m=106070797526891&w=2
> 
> No objections were raised - so I figure that its time to launch a 
> release vote.

On that roadmap:

! 1.1. evolution of the platform to provide equivalent
!      functionality together with migration tools supporting
!      Phoenix and Fortress user migration

I thought that meant a primary part of the release plan was support for 
phoenix and fortress, either through some compat layer and/or tools?

Is that finished? Where is it?

cheers!

- LSD



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Re: My feedback on Merlin & how about having a release?

Posted by Stephen McConnell <mc...@apache.org>.

Alexis Agahi wrote:

>Folks,
>
>I've just finished the portage of OpenIM http://open-im.net (Jabber Server) 
>using Merlin component manager.
>

Congratulations!

>
>OpenIM+Merlin seems now to be working pretty well: server still up after one 
>week of stress tests.
>

Guess what - it won't be long before you will be able to watch your 
stuff doing its stuff via JMX instrumentation.

>My opinion on using Merlin is positive. Component composition and 
>configuration is easy and powerfull. Block declaration is as simple as 
>powerfull. Project integration is easy when you understand some stuffs, but 
>to be honnest, Merlin documentation and tutorial are really helpfull. As I 
>wrote before, and considering my (small) experience of Phoenix & Forteress, 
>I've the feeling that Merlin stands perfectly beeteen these 2 compoment 
>managers.
>
>Now to help me to perform an official stable 1.1 OpenIM release, it should be 
>really nice if Merlin team could settle a stable binary release.
>

I agree.

A while ago I posted this proposed roadmap.

http://marc.theaimsgroup.com/?l=avalon-users&m=106070797526891&w=2

No objections were raised - so I figure that its time to launch a 
release vote.  I'll put together a vote on that later this evening 
together with breakdown of release status for the respective components.

Steve.

>
>Cheers
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org