+1
Farr, Aaron wrote:
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.
Purpose ======= To relieve current tensions on the Avalon platform; ensure stability for existing Avalon framework users; allow for development and enhancement of future versions.
Preface ======= 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 fixes.
Results ======= 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 that.
J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653
--
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
- Rich Cook
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
