avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hamilton Verissimo de Oliveira (Engenharia - SPO)" <hamilton.olive...@agenciaclick.com.br>
Subject Re: [avalon] State of Consensus
Date Fri, 05 Mar 2004 18:15:54 GMT
-----Mensagem original-----
De: Farr, Aaron [mailto:Aaron.Farr@am.sony.com]

> Okay, so perhaps we don't "officially" drop ECM/Fortress until Merlin has
> proper support.  But that doesn't mean we can't plan for it and work
> it.  That doesn't mean we can't tell our users, "Hey, Merlin is going to
> better.  Fortress and Phoenix are going away."  That doesn't mean we can't
> have a goal and a roadmap which states that what is now "Merlin" will one
> day be the "Avalon" container.

Pardon for my skepticism. I'd like to first have the first glimpse of
movement towards, then we can plan and tell users. I wearing the status quo
hat right now.

I know Avalon, and things always get forgotten for one reason or another.

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

View raw message