Menu
▾
▴
htdig-dev
|
From: Geoff H. <ghu...@us...> - 2003-05-25 07:14:37
|
STATUS of ht://Dig branch 3-2-x CHECKLIST FOR 3.2.0b5: * Add more items to checklist :-) * Must be able to (a) make check and (b) index www.htdig.org using "robotstxt_name: master-htdig" on all systems listed as "supported". Systems tested so far: - Mandrake 8.2, gcc 3.2 (lha, 21 May) - FreeBSD 4.6, gcc 2.95.3 (lha, 23 May) - Debian, Linux kernel 2.2.19, gcc 2.95.4 (lha, 23 May) Partly tested: - SunOS 5.8 = Solaris 2.8, gcc 3.1 (lha. Makes check. Big dig not tested) - SunOS 5.8 = Solaris 2.8, Sun cc with g++ 3.1 (lha. Compiles, fails check) To be tested: - RedHat anyone? - OS X anyone? * Latin-encodings (Gilles) * Check bugs listed in bug-tracker... * Polish release docs (Geoff) RELEASES: 3.2.0b5: Next release, June 2003??? 3.2.0b4: "In progress" -- snapshots called "3.2.0b4" until prerelease. 3.2.0b3: Released: 22 Feb 2001. 3.2.0b2: Released: 11 Apr 2000. 3.2.0b1: Released: 4 Feb 2000. (Please note that everything added here should have a tracker PR# so we can be sure they're fixed. Geoff is currently trying to add PR#s for what's currently here.) SHOWSTOPPERS: * Mifluz database errors are a severe problem (PR#428295) -- Does Neal's new zlib patch solve this for now? KNOWN BUGS: * Odd behavior with $(MODIFIED) and scores not working with wordlist_compress set but work fine without wordlist_compress. (the date is definitely stored correctly, even with compression on so this must be some sort of weird htsearch bug) PR#618737. * META descriptions are somehow added to the database as FLAG_TITLE, not FLAG_DESCRIPTION. (PR#618738) Can anyone reproduce this? I can't! -- Lachlan PENDING PATCHES (available but need work): * Additional support for Win32. * Memory improvements to htmerge. (Backed out b/c htword API changed.) * Mifluz merge. NEEDED FEATURES: * Quim's new htsearch/qtest query parser framework. * File/Database locking. PR#405764. TESTING: * httools programs: (htload a test file, check a few characteristics, htdump and compare) * Tests for new config file parser * Duplicate document detection while indexing * Major revisions to ExternalParser.cc, including fork/exec instead of popen, argument handling for parser/converter, allowing binary output from an external converter. * ExternalTransport needs testing of changes similar to ExternalParser. DOCUMENTATION: * List of supported platforms/compilers is ancient. (PR#405279) * Document all of htsearch's mappings of input parameters to config attributes to template variables. (Relates to PR#405278.) Should we make sure these config attributes are all documented in defaults.cc, even if they're only set by input parameters and never in the config file? * Split attrs.html into categories for faster loading. * Turn defaults.cc into an XML file for generating documentation and defaults.cc. * require.html is not updated to list new features and disk space requirements of 3.2.x (e.g. regex matching, database compression.) PRs# 405280 #405281. * TODO.html has not been updated for current TODO list and completions. I've tried. Someone "official" please check and remove this -- Lachlan * Htfuzzy could use more documentation on what each fuzzy algorithm does. PR#405714. * Document the list of all installed files and default locations. PR#405715. OTHER ISSUES: * Can htsearch actually search while an index is being created? * The code needs a security audit, esp. htsearch. PR#405765. |
|
From: J.E.J. op d. B. <ht...@op...> - 2003-05-26 10:36:48
|
Hi, ----- Original Message ----- From: "Geoff Hutchison" <ghu...@us...> To: <htd...@li...> Sent: Sunday, May 25, 2003 9:14 AM Subject: [htdig-dev] Current Status as of snapshot 3.2.0b4-20030525 > STATUS of ht://Dig branch 3-2-x > > CHECKLIST FOR 3.2.0b5: > * Add more items to checklist :-) > * Must be able to > (a) make check and > (b) index www.htdig.org using "robotstxt_name: master-htdig" > on all systems listed as "supported". Are these the conditions for a "well-functional" version? > Systems tested so far: > - Mandrake 8.2, gcc 3.2 (lha, 21 May) > - FreeBSD 4.6, gcc 2.95.3 (lha, 23 May) > - Debian, Linux kernel 2.2.19, gcc 2.95.4 (lha, 23 May) > Partly tested: > - SunOS 5.8 = Solaris 2.8, gcc 3.1 (lha. Makes check. Big dig not tested) > - SunOS 5.8 = Solaris 2.8, Sun cc with g++ 3.1 (lha. Compiles, fails check) > To be tested: > - RedHat anyone? > - OS X anyone? HP-UX 10.20 w/ GCC 2.8.1 > * Latin-encodings (Gilles) > * Check bugs listed in bug-tracker... > * Polish release docs (Geoff) |
|
From: Lachlan A. <lh...@us...> - 2003-05-27 10:48:48
|
On Mon, 26 May 2003 20:39, J.E.J. op den Brouw wrote: > Subject: [htdig-dev] Current Status as of snapshot 3.2.0b4-20030525 > > CHECKLIST FOR 3.2.0b5: > > * Must be able to > > (a) make check and > > (b) index www.htdig.org using "robotstxt_name: master-htdig" > > on all systems listed as "supported". > Are these the conditions for a "well-functional" version? I took the liberty of adding this section to the STATUS file, mainly=20 to promote discussion... They seem essentially minimal conditions for us to be able to say a=20 platform is "supported" rather than "supported, but..." If HP-UX can=20 be got to run but fails one of those tests, we can say exactly that=20 in the documentation. Do you agree? If you can think of any other=20 necessary conditions, please suggest them! > > To be tested: > HP-UX 10.20 w/ GCC 2.8.1 Excellent :) If you'd like a hand with that select(2) problem, I'd be=20 happy to look through your config.log file (but no promises I'll be=20 of any use). Cheers, Lachlan |
|
From: Neal R. <ne...@ri...> - 2003-05-27 22:51:56
|
Question: I've got a bunch of native win32 support changes I've been sitting on (and am now reverifying). Should I sit on them until we release 3.2.0b5?? What about fixes for memory leaks??? I'm back to a period here at work where I can work full-time on HtDig code itself to make it work natively with Win32.... Thanks. On Sun, 25 May 2003, Geoff Hutchison wrote: > STATUS of ht://Dig branch 3-2-x > > CHECKLIST FOR 3.2.0b5: > * Add more items to checklist :-) > * Must be able to > (a) make check and > (b) index www.htdig.org using "robotstxt_name: master-htdig" > on all systems listed as "supported". > Systems tested so far: > - Mandrake 8.2, gcc 3.2 (lha, 21 May) > - FreeBSD 4.6, gcc 2.95.3 (lha, 23 May) > - Debian, Linux kernel 2.2.19, gcc 2.95.4 (lha, 23 May) > Partly tested: > - SunOS 5.8 = Solaris 2.8, gcc 3.1 (lha. Makes check. Big dig not tested) > - SunOS 5.8 = Solaris 2.8, Sun cc with g++ 3.1 (lha. Compiles, fails check) > To be tested: > - RedHat anyone? > - OS X anyone? > * Latin-encodings (Gilles) > * Check bugs listed in bug-tracker... > * Polish release docs (Geoff) > > > > > > RELEASES: > 3.2.0b5: Next release, June 2003??? > 3.2.0b4: "In progress" -- snapshots called "3.2.0b4" until prerelease. > 3.2.0b3: Released: 22 Feb 2001. > 3.2.0b2: Released: 11 Apr 2000. > 3.2.0b1: Released: 4 Feb 2000. > > (Please note that everything added here should have a tracker PR# so > we can be sure they're fixed. Geoff is currently trying to add PR#s for > what's currently here.) > > SHOWSTOPPERS: > * Mifluz database errors are a severe problem (PR#428295) > -- Does Neal's new zlib patch solve this for now? > > KNOWN BUGS: > * Odd behavior with $(MODIFIED) and scores not working with > wordlist_compress set but work fine without wordlist_compress. > (the date is definitely stored correctly, even with compression on > so this must be some sort of weird htsearch bug) PR#618737. > * META descriptions are somehow added to the database as FLAG_TITLE, > not FLAG_DESCRIPTION. (PR#618738) > Can anyone reproduce this? I can't! -- Lachlan > > PENDING PATCHES (available but need work): > * Additional support for Win32. > * Memory improvements to htmerge. (Backed out b/c htword API changed.) > * Mifluz merge. > > NEEDED FEATURES: > * Quim's new htsearch/qtest query parser framework. > * File/Database locking. PR#405764. > > TESTING: > * httools programs: > (htload a test file, check a few characteristics, htdump and compare) > * Tests for new config file parser > * Duplicate document detection while indexing > * Major revisions to ExternalParser.cc, including fork/exec instead of popen, > argument handling for parser/converter, allowing binary output from an > external converter. > * ExternalTransport needs testing of changes similar to ExternalParser. > > DOCUMENTATION: > * List of supported platforms/compilers is ancient. (PR#405279) > * Document all of htsearch's mappings of input parameters to config attributes > to template variables. (Relates to PR#405278.) > Should we make sure these config attributes are all documented in > defaults.cc, even if they're only set by input parameters and never > in the config file? > * Split attrs.html into categories for faster loading. > * Turn defaults.cc into an XML file for generating documentation and > defaults.cc. > * require.html is not updated to list new features and disk space > requirements of 3.2.x (e.g. regex matching, database compression.) > PRs# 405280 #405281. > * TODO.html has not been updated for current TODO list and > completions. > I've tried. Someone "official" please check and remove this -- Lachlan > * Htfuzzy could use more documentation on what each fuzzy algorithm > does. PR#405714. > * Document the list of all installed files and default > locations. PR#405715. > > OTHER ISSUES: > * Can htsearch actually search while an index is being created? > * The code needs a security audit, esp. htsearch. PR#405765. > > > ------------------------------------------------------- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > _______________________________________________ > htdig-dev mailing list > htd...@li... > https://lists.sourceforge.net/lists/listinfo/htdig-dev > Neal Richter Knowledgebase Developer RightNow Technologies, Inc. Customer Service for Every Web Site Office: 406-522-1485 |
|
From: Gilles D. <gr...@sc...> - 2003-05-28 15:00:07
|
According to Neal Richter: > Question: I've got a bunch of native win32 support changes I've been > sitting on (and am now reverifying). > > Should I sit on them until we release 3.2.0b5?? > > What about fixes for memory leaks??? > > I'm back to a period here at work where I can work full-time on HtDig code > itself to make it work natively with Win32.... > > Thanks. Please don't sit on fixes for memory leaks, unless you have reason to believe the fixes are system specific and will likely cause the code to break on other systems. 3.2.0b5 isn't in a code freeze yet, and even if it were we try to get bug fixes in as much as possible in the pre-release period. Fixing memory leaks before the code is released is likely to benefit everyone, isn't it? As for the win32 support, I think it would be nice to include it if it won't delay the release too much. If it's likely to entail huge code changes requiring lots more debugging and testing time, and will push the release back more than a couple weeks, my own feeling would be to hold off on this until b5 is out. What do others think? -- Gilles R. Detillieux E-mail: <gr...@sc...> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) |
|
From: Lachlan A. <lh...@us...> - 2003-05-28 23:53:03
|
I agree -- win32 will be nice if the delay is up to a week or so, but=20 isn't worth delaying b5 too long for. $0.02 Lachlan On Thu, 29 May 2003 00:59, Gilles Detillieux wrote: > As for the win32 support, I think it would be nice to include it if > it won't delay the release too much. If it's likely to entail huge > code changes requiring lots more debugging and testing time, and > will push the release back more than a couple weeks, my own feeling > would be to hold off on this until b5 is out. What do others > think? |
Thanks for helping keep SourceForge clean.
X