Berin Loritsch wrote:
Please be more specific.-----Original Message----- From: Neeme Praks [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 9:45 AM To: Avalon Developers List Subject: Re: [VOTE] Plans to move aheadBerin Loritsch wrote:Development Plan 1: We continue to support our existing projects while we start fresh on a new effort. The new effort will be a scalable container that follows a "profile". Basically the container will only use the features that are part of that profile and ignore everything else. Development Plan 2: We adapt our current projects to the three/four tiered approach (Tutorial, Micro, Standard, Enterprise). This is probably an easier migration path, and it would leverage the existing code that we already have.
Seems to me that you have missed the 3rd alternative:
We continue to support our existing projects while we take the best parts of the existing code into the new "tiered" model container.
(and I do not believe that you were seriously proposing plan 2, as that seems to imply NOT SUPPORTING EXISTING projects)
Sorry to be confusing, but I thought that was implied for Dev plan 2. Which model do you prefer?
What "existing projects" should we support?
Released are ECM and Phoenix, and they will be supported anyway.
Fortress and Merlin would in either case go into the new container, as I see it counterproductive to keep them separated.
Proposal 3
1 Phoenix is supported and put in feature freeze.
2 Merlin and Fortress united
3 a micro profile is made from them
4 Phoenix is made to use "Merlin and Fortress united" as a container
Or something along these lines.
Note that step two could imply that we start anew including selective parts of both efforts.
--
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]>
