Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 13198 invoked from network); 13 Jul 2004 20:41:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Jul 2004 20:41:09 -0000 Received: (qmail 22650 invoked by uid 500); 13 Jul 2004 20:41:09 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 22389 invoked by uid 500); 13 Jul 2004 20:41:07 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 22375 invoked by uid 99); 13 Jul 2004 20:41:07 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [170.190.17.220] (HELO jismsg1.nashville.org) (170.190.17.220) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 13 Jul 2004 13:41:04 -0700 Received: by jismsg1.nashville.org with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jul 2004 15:44:15 -0500 Message-ID: From: "Bennett, Timothy (JIS/Applications)" To: 'Avalon Developers List' Subject: RE: [PROPOSAL] End the drama Date: Tue, 13 Jul 2004 15:41:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: Stephen McConnell [mailto:mcconnell@apache.org] > 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? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org