Leo Simons wrote:
Berin Loritsch wrote:
Ok. So the migration path would be:
Milestone 1: ECM replacement (Codename: Fortress)
Milestone 2: Proper Meta Model (Codename: Merlin)
Milestone 3: Pluggable container (Codename: ?Uber Container?)
Note that we might want smaller milestones between Merlin and Uber....
Drop the "uber"
---------------
I want the "uber container" term dropped from the planet.
+1
I already proposed a different codename somewhere, I believe I called it
Spearhead.
Cool!
Working title
-------------
Besides codenames, we need a working title for the project. I resent
"Avalon Container", as there's more avalon containers than just this
effort (for example EOB). I suggest a working title of
*Avalon ESCA*, the Avalon Extensible Scalable Container Architecture
Spearhead gets +1 for me as a codename.
Roadmap
-------
Avalon will be focussing container development into two efforts. The
first one is the creation of Avalon ESCA. To this end, most existing
avalon container projects will refocus to be part of that goal.
The roadmap for this effort is roughly as follows:
Milestone 1: ECM replacement (Codename: Fortress)
Milestone 2: Proper Meta Model (Codename: Merlin3)
Milestone 3: Phoenix Compatible (Codename: Phoenix5)
Milestone 4: Profileable, pluggable container (Codename: Spearhead)
The second container development effort is the maintainance of existing
released efforts with an existing userbase, ie phoenix. This will merge
into the ESCA effort when there is an ESCA release compatible with those
existing efforts.
graphically:
====================================================================
ECM --> Fortress --> Merlin3 --> Phoenix5 --> Spearhead --> ...
^ ^ ^
| : |
Merlin1&2 (unreleased)-| : |
All other | :(synergy) |
container dev code -/ : |
: |
Phoenix4 -------------------------------/
====================================================================
+1
It's better than what I wrote before, I'm all for it.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
