Re: LYNX-DEV Lynx "release" page and pre-release of v2.8

[Foteos Macrides]

Klaus Weide <address@hidden> wrote:
>I have started <URL:http://sol.slcc.edu/lynx/release2-8.html>.
>It's obviously not complete, but at least it is a place to point to.
>(Scott should decide whether that's OK as a semi-permanent location.)
>
>The summary of changes there is off the top of my head, just some changes
>that came to mind that might be important to a lot of users.  I have
>probably overlooked a lot of things; if there is something you feel should
>be listed there, please speak up.
>
>There currently is no "pre-release" code set different from the usual
>"development code".  The changes that come to mind to make the devel-code
>-> Lynx 2.8 switch are basically replacing the string 2.7.1 (or 2-7-1) in
>a lot of places, an renaming "CHANGES.new" to "CHANGES".  (Is there
>something I have overlooked, Henry?  Some SIMPLEDIR changes remaining
>to be done?  You haven't updated SIMPLEDIR.gz in a while.)

        Could you change that to an http://sol.slcc.edu/lynx/release/
directory tree (with an index.html, not release2-8.html in /lynx/) so
that the URL references neither a version nor a person, and thus will
never again need to be modified in the Lynx home page and Subir's
"Lynx links"?

        Also, please include a link in that index.html to the current
release (v2.7.1), which could be a document based on modifications
of /lynx/fote/index.html, but with another name, which does reference
the version, is in /lynx/release/, and provides access to that version
(as the current release, now, and as an old release starting a few days
before Christmas) in some place other than the /lynx/fote/ tree.  This
would be better than what you have now -- a reference to the Lynx home
page, which points to /lynx/fote/ and still cannot be changed to point
to /lynx/release/ until the moment of release a few days before Christmas.

        Similarly, please move /lynx/fote/patches/security.html to the
/lynx/release/ tree and point to it there.

        If you do not have an actual pre-release in the /lynx/release/
tree, packaged as it will be for the actual release, but still subject
to bug fixes and tweaks until a few days before Christmas, then you have
not yet offered a pre-release.  A link back to the devel code as presently
structured is not a pre-release (unless you're planning to put out just an
EXP_RELEASE :).

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================