lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV post-release distribution site configuration


From: T.E.Dickey
Subject: Re: LYNX-DEV post-release distribution site configuration
Date: Mon, 9 Mar 1998 21:01:06 -0500 (EST)

> to follow up on what T.E.Dickey said:
> 
> > btw, while we're on the topic:  I think it's best to make a page that
> > covers both 2.8 and 2.7.2 - essentially move Fote's page & link to that,
> > with a summary of the differences.  At the moment there's a directory
> > named 'release', which Fote created, and I think there's room for 2.8
> > there as well - but the index.html should be adjusted.
> 
> I believe this violates the model that Fote clearly indicated
> over and over.  The release/ directory or URL tree is for the
> current release of which there is only ever one.  Talk to Scott.
> release/ may simply be a soft pointer, moved to the latest in a
> series of version-numbered directories.
that might work (I had it stuck in my head that 'release' would be a
directory.  But /lynx/release2-7-2 and /lynx/release2-8 would work (if
/lynx/release points to the latter ;-).
 
> You can install a front page as the default document within the
> Lynx-2-8 directory tree which acknowledges and links to a start
> page for 2.7.2, but it should be discussed with "supersedes"
> semantics.  In what you get when you navigate to release/ it
> should not be given equal treatment.
I don't plan to make it equal (obviously I'm biased), but don't think it
proper to discard it altogether, particularly since there are details in it
that I'll still be referring to & comparing against during the next set of
changes.  I'll make a draft & get Scott's opinion.  (It's his webpage after
all).
 
> I believe that I am articulating namespace principles that Fote
> would support [as he clarified them].
Fine (I brought up the topic because I wanted feedback).
 
> Al Gilman
> 


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]