I'm getting a little ahead of myself, but I wrote up the basics for a pre-release and release checklist. I don't think I left anything out, but please let me know if I did. I'll put these up on dev.htdig.org sometime today. -Geoff Pre-release: 1) Ensure compilation on a variety of platforms*, pref with several compilers (gcc-2.7.2, gcc-2.8.1, egcs-1.1.2, gcc-2.95) with "-W -Wall" 2) Minimize the number of compiler warnings: none should come up without -W -Wall explicitly and very few even with these flags. 3) Check all components for obvious faults. 4) Test on www.htdig.org, any other important test websites, and test suite. 5) Run LeakTester, checker, purify or equivalent memory-leak detector. 6) Run gprof and generate a profile report of *at least* htdig and htsearch. 7) Re-run steps 1-5 as needed (e.g. if other steps introduce significant changes). 8) Make a snapshot as a pre-release candidate. Release: 1) Update .version 2) Update README 3) Update htdocs (check RELEASE.html and copy ChangeLog) 4) Update htdocs/THANKS.html 5) Tag the CVS tree for release 6) Make a release tar 7) Make a release diff 8) Sync maindocs and htdig3/htdocs, ensuring the next website update will include the new version. 9) Upload the tar and diff to files 10) Make announcements ([EMAIL PROTECTED], [EMAIL PROTECTED], freshmeat.net, lwn.net, ...) *Platforms: At *least* these (some of these have seen problems in the past): Linux libc5, glibc2.0, glibc2.1 Solaris 2.5, 2.7 Digital 4.0X IRIX 5.3, 6.2 Obviously, any platforms we can get our hands on for testing would be very useful. ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] containing the single word "unsubscribe" in the SUBJECT of the message.
