Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 33460 invoked from network); 15 Nov 2003 01:29:40 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Nov 2003 01:29:40 -0000 Received: (qmail 53213 invoked by uid 500); 15 Nov 2003 01:29:20 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 53066 invoked by uid 500); 15 Nov 2003 01:29:19 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 53052 invoked from network); 15 Nov 2003 01:29:19 -0000 Received: from unknown (HELO www2.kc.aoindustries.com) (65.77.211.84) by daedalus.apache.org with SMTP; 15 Nov 2003 01:29:19 -0000 Received: from dialup-22.147.220.203.acc01-aubu-gou.comindico.com.au (dialup-22.147.220.203.acc01-aubu-gou.comindico.com.au [203.220.147.22]) (authenticated) by www2.kc.aoindustries.com (8.11.6/8.11.6) with ESMTP id hAF2UQC24661 for ; Fri, 14 Nov 2003 20:30:27 -0600 Subject: filename for cocoon-latest.* on mirror.cgi From: David Crossley To: dev@cocoon.apache.org In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1068859757.19383.25430.camel@ighp> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 15 Nov 2003 12:29:17 +1100 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: > I just added the current version information to the mirror page, > so when you go to that page, you see to which version "latest" > relates. > > Thanks for the hint. That is a bit better, but Andrew hints at other issues. When they download the archive, then the filename just says "latest" on their disk. Sure, they should just rename it with a version number. He also refers to the problem when you browse the "cocoon/" directory "Latest releases and milestones" there may be confusion. Why do we need the "latest"? They can easily see by the date and version number. I suppose that it adds one more task to our release process to modify the mirror.html page. --David > > -----Original Message----- > > From: AndrewWatt2001@aol.com [mailto:AndrewWatt2001@aol.com] > > Sent: Friday, November 14, 2003 10:22 AM > > To: cziegeler@s-und-n.de > > Subject: Re: [ANN] Apache Cocoon 2.1.3 Released > > > > > > Hi, > > > > With all due respect can I suggest that the current way of distributing > > Cocoon is plain daft! > > > > On http://cocoon.apache.org/mirror.cgi there is a file > > cocoon-latest-src.zip. Great until a week or a month or 2 months down the > > line. When the latest file will, presumably, still be > > cocoon-latest-src.zip. > > > > So, how do I easily tell then whether I need to download and upgrade? I > > can't, at least not easily. > > > > Why not use the traditional system of giving the version a > > NUMBER? It allows > > comparison of whether I have, or have not, the latest version. > > > > Yes, I found that there is a numbered version of 2.1.3 at > > http://ftp.plig.org/pub/apache/dist/cocoon/SOURCES/ but why use this silly > > cocoon-latest-src.zip idea at all? Good for lazy Web page authors > > who don't > > want to have to update the page perhaps? But not good for users. > > > > It just seems daft to me. > > > > Andrew Watt > > P.S. I *do* appreciate the good work you guys do, but "little things" like > > this are very frustrating. > >