Now that a plan seems to be falling into place, I'd like to see a migration roadmap for those of us using the Avalon technology.
ah....you can plan all you like in OSS, but in the end it depends on people doing actual work. Lesson learned from the last few months (esp. the road to fortress 1.0) is that any roadmap will contain many flaws.
There have been some updated releases, and it seems that there are going to
be some refreshes to coincide with the Merlin release.
indeed.
> What I'd like to
know is the plan for the remaining parts, including Cornerstone and Phoenix.
Are we going to have one?
Cornerstone: yes, since steve has volunteered. Phoenix4.1: not sure. No-one seems to want to do the work atm.
What should those of us deploying on Phoenix expect to do in terms of upgrading our Avalon technologies, and when?
For now, nothing. At some point X in the future (X being, "when it is done"), it is hoped that merlin will be able to support all phoenix users. That is a big prerequisite :D. At that stage, we will discuss how to proceed. The *current* plan Berin came up with involves retiring phoenix and migrating users to merlin. So you will likely be asked to evaluate whether merlin does what you need it to, there will be a time where it is changed to make sure it does what everyone needs it to, then there'll be a release or two, then phoenix might be retired.
My plan involves not making any kind of bold statement or decision on any of that until Merlin3.2 is actually there and functional. But the revised roadmap might look like:
The Container Picture ---------------------
--------------------------------------------------time----------->
+----+ +--------+ +------------+
|ECM |-->|Fortress|-->|Fortress1.1?|-----+----------------------?
+----+ +--------+ +------------+ |<embeddable>
|
+-------+ +----------+ +----------+
|Merlin3|-------->|Merlin3.1?|--->|Merlin3.2?|
+-------+ +----------+ +----------+
|
+--------+ +-------------+ |
|Phoenix4|----------->|Phoenix4.1.x?|----------------------+-----?
+--------+ +-------------+ <compatibility layer>
---------------------------------------------------------time---->whether phoenix 4.1 will be released we dunno. I think either Paul or Peter need to handle that and I'm not sure they have the time and/or desire to do so anytime soon. If someone steps up to be phoenix release manager it will happen.
The Component Picture
---------------------
Migration of avalon-excalibur into avalon-components is pending, my desire to do the work (or anyone elses' desire) being the main issue. I suspect we'll have several point releases of several of the excalibur components; when someone steps up to do release management on sourceresolve and xmlutil I think those might get a release as well. Avalon-components/cornerstone is pending releases (nothing else left to be done there, I think), Steve has promised several times to get on it and I suspect he will if we keep pestering him about it ;)
--------------------------------------------------------------time---->
+---------------+ +-----------------+
|Big-Cornerstone|--->|Avalon-Components|-------------------------------
+---------------+ +-----------------+ <releases> <releases> |
|
+---------+ <some releases> |
|Excalibur|--------------------------------------------------------+
+---------+ <some releases> <some releases>+------+
|Logkit|------------------------------------------------+-------------?
+------+ |
<Log4J2 intending to |
+-----+ incorporate lots +------+
|Log4J|--------------------------------------------->|Log4J2|
+-----+ of logkit features>+------+
--------------------------------------------------------------time---->The Innovation Picture
----------------------
I might just become "Chief Executive In Charge Of Smart Dynamic Proxying". The plan I woke up with this morning is to start a 'merlin-magic' project that will be a full, clean, transparent and performant support layer for pico-style, nano-style, xwork-style, spring-style, hivemind-style, eob-style, whatever-other-project-style components. Stuff like
MerlinBasedPicoContainer implements PicoContainer
{
MerlinBasedPicoContainer( DefaultAppliance appliance )
{ /* ... */ }
}another personal plan is to add the great altrmi support eob enjoys in there to show the world what a joy working with altrmi really is.
cheers,
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
