Bennett, Timothy (JIS/Applications) wrote:
-----Original Message-----
From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 3:33 PM
To: Avalon Developers List
Subject: Re: [PROPOSAL] End the drama
peter royal wrote:
I propose:
* Bump to Avalon 5.
* On front page, under products, list:
Current:
Merlin
Legacy:
Avalon Framework
Components & Containers
* Legacy Avalon-Framework will goto the 4.1 API docs and
its limited
documentation
* Legacy Components & Containers will links to similar
verbage as on
the download page.
The past will not be hidden, and a clean line will be drawn
for the future.
-pete
Sorry - this does not make sense.
Avalon Framework is not legacy, Components are not legacy.
No - there are much better solutions - solutions that are based on proper management of the documentation to properly reflect the realities of the past and the realities of the present.
Yeah... I don't view either the Components or the Framework as legacy, because they are not. Advertising them as legacy bits would send an equally confusing message to users as would advertising them as products.
How about giving the team some time to produce alternative views of the site to see if we can come to some agreement and consensus. I believe the team agrees that the some things need to change on the site, so how about agreeing to review some alternatives?
+1
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
