Re: LYNX-DEV new release?

[T.E.Dickey]

> > It's more/less up to Klaus, as far as I'm concerned.  I have a half-dozen
> > small things to polish off (but have been preparing a large change for 
> > another
> > program).
> 
> Well, as far as I am concerned - for making the "devel" code into a
> non-devel "release" there are a number of things to be done.
... 
> More general, things where work by the list or least input is required.
> - What to do about the two ways of parsing.  Keep both (and find a better
>   key, command line switch, document); or come up with a
>   combined/compromise mode (or even both).
> - What about the security stuff jss was working on?
that seems to have gotten lost. (my preference for the whole affair is
to move those chmod's  and so forth down into a common function that would
hide those details).

> - Documentation of installation procedures.  For example, the file
>   INSTALLATION doesn't know anything about ./configure.
ok.

> - Documentation of various things yet undocumented.
> - More testing.
ok.  I did a series of builds at #48, but haven't had time to build since.
 
-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;