> While it will be possible, I would like people to concentrate on the
> existing 6.4 issues we have, and discourage parallel development on
> separate final and features source trees.
As Bruce describes, a "quiet time" just before and up to a month after a
major release is a _really_ good idea. For a couple of reasons:
1) it lets us put out bugfix releases with a minimum of trouble
2) it lets people planning larger changes for the next release to work
on a stable, quiet tree, with some assurance that they will likely be
able to remerge their work when things unfreeze.
imho we made a few too many changes (leading to uncertainties in exactly
how much had changed, and uncertainty in how much might be newly broken)
in the v6.3->v6.3.1->v6.3.2 release series, and we should try to be even
quieter this time around.
Bruce, can you add the following items to the ToDo for docs:
> Docs
> ----
> generate html/postscript documentation
(User's Guide, Administrator's Guide, Programmer's Guide) (Thomas)
> make sure all changes are documented properly (All)
markup and merge JDBC docs from Peter (Thomas, others??)
merge the release notes into doc/src/sgml/release.sgml (Bruce, Thomas)
generate new text-format INSTALL and README from sgml sources (Thomas)
Thanks.
- Tom
