IMHO, this question highlights the need to get 3.2.0b[45] out ASAP. Am I correct in believing that the hold-up is basically database errors? If so, could we set a target "acceptable bug level" just to get the other bug-fixes/features out there? After all, people who are savvy enough to run betas are able to choose to keep using 3.2.0b3 if they want.
I don't know anything about the database code, but if someone points the way, I'm happy to spend some time working on it. Do we need a test dataset which reproducibly tickles a bug? Cheers, Lachlan On Saturday 18 January 2003 02:32, Geoff Hutchison wrote: > To quote Mark Twain... "Reports of my demise have been greatly > exaggerated." ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
