Re: a new release

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dumas Patrice wrote:

|>|* use texi2html/Conf instead of texi2htmlrc ?
|>
|>This last one too I still prefer since it is more extensible in an
|>organized fashion.
|
|
|The file name is Config and no Conf, since it holds the Texi2HTML::Config
|namespace. Is it right ?


This is fine with me.

|If it is, I think a release can be done.


I think that doc should catch up first.  At least enough so that an
upgrading user can port their old configuration files forward.  It would
be pretty rude to let a user upgrade and break a configuration without
at least warning them.

If you wouldn't mind noting other major features and bug fixes in the
NEWS file as well, I would appreciate it and, I'm sure, so would our
users.  The usual guideline is, again, at least one summary line for
each major bug fix or feature, with more when necessary.  The NEWS file
doesn't need nearly as much detail as the ChangeLog, of course.  Just
blurbs summarizing major functionality, e.g. "@ifhtml works!".  You can
glance through the existing NEWS file for examples, but IMO, the
texi2html NEWS file has been too sparse in the past.  The CVS NEWS file
might hold a better example of what I have in mind.

Derek

- --
~                *8^)

Email: [email protected]

Get CVS support at <http://ximbiot.com>!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/bwjwLD1OTBfyMaQRAochAKCfOltHRJK5PrHyUh57yDLfWS4eswCfZtu4
JWtPbMD4UZ78riidHgNsAF0=
=SSVf
-----END PGP SIGNATURE-----