avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farr, Aaron" <Aaron.F...@am.sony.com>
Subject [PROPOSAL] Avalon 5
Date Mon, 12 Jul 2004 19:16:13 GMT
Okay, trying to stop the flames and get back to constructive proposals.

This is an actual "proposal" in the sense that I'd like to gauge the support
for it and, if necessary, move it to a vote.

To relieve current tensions on the Avalon platform; ensure stability for
existing Avalon framework users; allow for development and enhancement of
future versions.

The idea of "Avalon 4" versus "Avalon 5" is more than just the version
number of the framework jars.  Avalon 4 has referred informally to the
entire Avalon platform.  If we think of Avalon as a single product, then
Avalon 4 refers to the entire suite of Avalon projects at the time: Avalon
framework, Fortress, Merlin, Excalibur, Phoenix, etc.

Basic Plan
Label the current Avalon-Merlin platform as presented in the current website
(specifically the 'specification section') as Avalon 5.

Present Avalon 4 as a separate "product" which would include: the
Avalon-Framework jars, javadocs, and related documentation.  An SVN branch
will be created that will be considered STABLE and will only accept bug

Avalon clients and sister projects such as Excalibur will be assured that
Avalon 4 will remain stable.  They can continue to develop products based on
'classic' Avalon or they can chose to use the newer and better defined
Avalon 5 platform.  As Berin pointed out, this gives us all, users and
developers alike, a "line in the sand."

I just want this to all be behind us and I believe this proposal will allow

J. Aaron Farr
  (724) 696-7653

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

View raw message