Menu
▾
▴
htdig-dev
|
From: Geoff H. <ghu...@us...> - 2003-02-02 08:16:24
|
STATUS of ht://Dig branch 3-2-x
RELEASES:
3.2.0b5: Next release, tentatively 1 Feb 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)
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:
* Field-restricted searching. (e.g. PR#460833)
* 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)
* Add thorough documentation on htsearch restrict/exclude behavior
(including '|' and regex).
* 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.
* 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: Lachlan A. <lh...@us...> - 2003-02-02 08:50:11
|
Greetings all, Is there a list of tasks which *must* be completed before the release=20 of 3.2.0b4/5? If the "STATUS" file is that list, can I suggest that=20 some things be classed as "not essential" (at least defaults.xml, and=20 preferably most of it)? If STATUS isn't the list, could one be drawn=20 up? Sorry for sounding impatient, and I know that everyone is busy, but it=20 is two months after the initial target release date, and I don't feel=20 much closer... Thanks! Lachlan |
|
From: Geoff H. <ghu...@ws...> - 2003-02-03 14:55:43
|
> Is there a list of tasks which *must* be completed before the release > of 3.2.0b4/5? If the "STATUS" file is that list, can I suggest that > some things be classed as "not essential" (at least defaults.xml, and > preferably most of it)? The STATUS file is the list, though it's intended to be updated by other developers too! I've put everything in the STATUS list, though I agree that defaults.xml either needs to shape up soon or be left out of 3.2.0b5. I would definitely say that this zlib compression issue is a "showstopper" at the moment. > Sorry for sounding impatient, and I know that everyone is busy, but it No, good for you to bring this up and make some noise. :-) Why don't you propose a list of what you think is essential for 3.2.0b5. -Geoff |
|
From: Ted Stresen-R. <ted...@ma...> - 2003-02-03 15:25:39
|
> defaults.xml either needs to shape up soon Could you provide some details on what it needs, on what's missing? Ted Stresen-Reuter |
|
From: Lachlan A. <lh...@us...> - 2003-02-10 12:02:54
|
Greetings all, This are my list of *bare essentials* for 3.2.0b5 and a tentative=20 release schedule to get it out in about three weeks. Comments on=20 both are invited... =20 TO-DO LIST ~~~~~~~~~~ SHOWSTOPPER: * Still need thorough testing of the database, with Neal's zlib patch Any ideas how we can test this thoroughly? TESTING: * httools programs: (htload a test file, check a few characteristics, htdump and compare) * Test field restricted searching DOCUMENTATION: * Split attrs.html into categories for faster loading. (i.e., commit Ted's scripts) * 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. * Document the list of all installed files and default locations. PR#405715. * (Update version number from 3.2.0b4 to 3.2.0b5) TENTATIVE SCHEDULE ~~~~~~~~~~~~~~~~~~ Fri 14 Feb: Last additions to the above TO-DO list Fri 21 Feb: Feature freeze. =09 No new features added. All available development =09 effort for testing, bug fixes, documentation and =09 configure/install issues Fri 28 Feb: Code freeze. Testing and documenting only. =09 Update version number throughout. Fri 7 Mar: Release. On Tuesday 04 February 2003 01:55, Geoff Hutchison wrote: > > Is there a list of tasks which *must* be completed before the > > release of 3.2.0b4/5? > The STATUS file is the list > I would definitely say that this zlib compression issue is a > "showstopper" at the moment. > > Why don't you propose a list of what you think is essential for > 3.2.0b5. |
|
From: Ted Stresen-R. <ted...@ma...> - 2003-02-10 14:00:02
|
The defaults.dtd and defaults.xml documents should also be diff'd and committed as I had to make minor changes to both to get the Xalan processor to process them. As I recall, in the dtd I had to change one of the attribute types from NUMERIC (which is not, apparently, a valid attribute type) to CDATA and in defaults.xml there was one incorrect tag (it was opened as "href" and closed as just "ref"). Also, we should probably import the htdig.css style sheet into the archive as well. Thanks for the positive feedback. It's nice to know that after all these years using htdig (sometimes for commercial endeavors) I'm finally able to give something back! Ted On Monday, February 10, 2003, at 05:58 AM, Lachlan Andrew wrote: > * Split attrs.html into categories for faster loading. > (i.e., commit Ted's scripts) |
|
From: Lachlan A. <lh...@us...> - 2003-02-20 22:57:51
|
Greetings Geoff, Do you have any comments on my previous post about the to-do list and=20 release schedule for 3.2.0b5? It would be nice to have an official=20 list and schedule (or to know that a schedule is premature). Thanks :) Lachlan On Monday 10 February 2003 22:58, Lachlan Andrew wrote: > This are my list of *bare essentials* for 3.2.0b5 and a tentative > release schedule to get it out in about three weeks. Comments on > both are invited... > > TO-DO LIST > ~~~~~~~~~~ > SHOWSTOPPER: > * Still need thorough testing of the database, with Neal's zlib > patch Any ideas how we can test this thoroughly? > TESTING: > * httools programs: (htload a test file, check a few > characteristics, htdump and compare) > * Test field restricted searching > DOCUMENTATION: > * Split attrs.html into categories for faster loading. > (i.e., commit Ted's scripts) > * 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. > * Document the list of all installed files and default > locations. PR#405715. > * (Update version number from 3.2.0b4 to 3.2.0b5) > > TENTATIVE SCHEDULE > ~~~~~~~~~~~~~~~~~~ > Fri 14 Feb: Last additions to the above TO-DO list > Fri 21 Feb: Feature freeze. > =09 No new features added. All available development > =09 effort for testing, bug fixes, documentation and > =09 configure/install issues > Fri 28 Feb: Code freeze. Testing and documenting only. > =09 Update version number throughout. > Fri 7 Mar: Release. > > On Tuesday 04 February 2003 01:55, Geoff Hutchison wrote: > > > Is there a list of tasks which *must* be completed before the > > > release of 3.2.0b4/5? > > > > The STATUS file is the list > > I would definitely say that this zlib compression issue is a > > "showstopper" at the moment. > > > > Why don't you propose a list of what you think is essential for > > 3.2.0b5. On Friday 21 February 2003 05:12, Gilles Detillieux wrote: > You don't need anyone's permission to commit to cvs, > as long as there isn't a feature freeze in place, which there isn't > for 3.2.0b4/b5.=20 |
|
From: Geoff H. <ghu...@ws...> - 2003-02-22 05:19:25
|
Well, I had an oral exam on Thursday, so I've been quite busy the last few weeks and fortunately things should settle down a bit. (I can't say I followed much e-mail unless my filters threw it into the "Family" mailbox, sorry.) >> SHOWSTOPPER: >> * Still need thorough testing of the database, with Neal's zlib >> patch Any ideas how we can test this thoroughly? Seems like you've got a pretty good start so far. I'd be glad to run some larger-scale digs under Mac OS X. Is there another platform we can throw into the mix Neal? I can offer RH8.0 as well, but I don't know that this would shed any new light on things. As far as a large-scale test, I'd be glad to tar up the htdig.org website including mail archives. >:-) >> TESTING: >> * httools programs: (htload a test file, check a few >> characteristics, htdump and compare) I haven't written an actual test-suite script for this, but I do run these tests by hand. If anyone has any suggestions on what all I should be testing, please let me know. >> * Test field restricted searching Lachlan, does this fall into your area? >> DOCUMENTATION: >> * Split attrs.html into categories for faster loading. >> (i.e., commit Ted's scripts) Hmm. Let's see how this comes along. It's nice right now, but I don't know that we'd want to put it in a release within a few weeks. But any decision on that can wait. >> Fri 14 Feb: Last additions to the above TO-DO list >> Fri 21 Feb: Feature freeze. >> No new features added. All available development >> effort for testing, bug fixes, documentation and >> configure/install issues I don't see any reason we shouldn't stick to a feature freeze. Is there any feature we're somehow leaving out right now? >> Fri 28 Feb: Code freeze. Testing and documenting only. >> Update version number throughout. >> Fri 7 Mar: Release. This may be ambitious. I've never knowingly sent out a release that had a database bug. So we obviously want to kill that SHOWSTOPPER soon. Neal, how much time do you have to devote to the bug? Would it help for me to set up valgrind on my RH box? -Geoff |
|
From: Gabriele B. <bar...@in...> - 2003-02-23 08:33:24
|
>I don't see any reason we shouldn't stick to a feature freeze. Is there >any feature we're somehow leaving out right now? There's my cookies input file feature. I am ready now to commit it (after I have reviewed it according to Gilles' suggestion). Ciao -Gabriele -- Gabriele Bartolini - Web Programmer - ht://Dig & IWA Member - ht://Check maintainer Current Location: Prato, Tuscany, Italia bar...@in... | http://www.prato.linux.it/~gbartolini | ICQ#129221447 |
|
From: Lachlan A. <lh...@us...> - 2003-05-17 05:30:23
|
Greetings all, I've lost track, but my current understanding is: 1. The bug causing a database crash doing the *second* dig using -i has been fixed. 2. Other than under OS X, no other database bugs have been seen. Anybody, ** PLEASE CORRECT ME IF THAT IS WRONG ** 3. OS X is a basket case (at least on the compile farm) because libtool fails to link the C++ dynamic libraries (which aren't even there on the compile farm!). Geoff, what should we do to test/prove that the "showstopper" is fixed=20 (on all systems on which ht://Dig links)? Will someone who knows OSX=20 try to fix that issue, or can we release 3.2.0b5 for Linux, FreeBSD,=20 Solaris, ...? If there *is* a residual database eror, the sooner we release 3.2.0b5 =20 and get a large number of users running it, the sooner we'll be able=20 to find it and get 3.2R out. Geoff, Gilles, even if you don't have time for testing/debugging,=20 could I be bold enough to ask for some more hands-on leadership? I=20 feel lost... Thanks!! Lachlan On Sat, 22 Feb 2003 16:19, Geoff Hutchison wrote: > >> SHOWSTOPPER: > >> * Still need thorough testing of the database, with Neal's zlib > >> patch Any ideas how we can test this thoroughly? > > As far as a large-scale test, I'd be glad to tar up the htdig.org > website including mail archives. >:-) > > >> Fri 28 Feb: Code freeze. Testing and documenting only. > >> =09 Update version number throughout. > >> Fri 7 Mar: Release. > > This may be ambitious. I've never knowingly sent out a release that > had a database bug. So we obviously want to kill that SHOWSTOPPER > soon. |
|
From: Jim C. <li...@yg...> - 2003-05-17 06:32:18
|
On Friday, May 16, 2003, at 11:30 PM, Lachlan Andrew wrote: > 2. Other than under OS X, no other database bugs have been seen. > Anybody, ** PLEASE CORRECT ME IF THAT IS WRONG ** The patch you provided seemed to correct the last of the consistently repeatable database problems under OS X. I ran into one database problem after applying that patch but was never able to reproduce it a second time. > Geoff, what should we do to test/prove that the "showstopper" is fixed > (on all systems on which ht://Dig links)? Will someone who knows OSX > try to fix that issue, or can we release 3.2.0b5 for Linux, FreeBSD, > Solaris, ...? The problem with building under OS X is limited to dynamic builds. Even without correcting that problem, a fully functional install under OS X is still possible with a static build. As such, I don't personally see this issue as being any sort of show stopper. If it becomes a common issue, we can always add a FAQ. There is also still an issue with 'make check' under OS X, but again that doesn't seem like it should be a show stopper. I will continue to look at the OS X problems as I find time. Jim |
|
From: J.E.J. op d. B. <ht...@op...> - 2003-05-17 14:30:50
|
Hi all, There is a ./configure issue on HP-UX 10.20 about select(2) not found in de db tree. I'm trying to get the problem fixed, but 'm not sure how long it will take. ----- Original Message ----- From: "Lachlan Andrew" <lh...@us...> To: "Geoff Hutchison" <ghu...@ws...> Cc: <htd...@li...> Sent: Saturday, May 17, 2003 7:30 AM Subject: [htdig-dev] Re: Release schedule for 3.2.0b5? > Greetings all, > > I've lost track, but my current understanding is: > > 1. The bug causing a database crash doing the *second* dig using -i > has been fixed. > 2. Other than under OS X, no other database bugs have been seen. > Anybody, ** PLEASE CORRECT ME IF THAT IS WRONG ** > 3. OS X is a basket case (at least on the compile farm) because > libtool fails to link the C++ dynamic libraries (which aren't even > there on the compile farm!). > > Geoff, what should we do to test/prove that the "showstopper" is fixed > (on all systems on which ht://Dig links)? Will someone who knows OSX > try to fix that issue, or can we release 3.2.0b5 for Linux, FreeBSD, > Solaris, ...? > > If there *is* a residual database eror, the sooner we release 3.2.0b5 > and get a large number of users running it, the sooner we'll be able > to find it and get 3.2R out. > > Geoff, Gilles, even if you don't have time for testing/debugging, > could I be bold enough to ask for some more hands-on leadership? I > feel lost... > > Thanks!! > Lachlan --jesse |
|
From: Lachlan A. <lh...@us...> - 2003-05-24 14:57:32
|
Greetings all, A brief update on the testing: I've fixed the configure process for FreeBSD 4.6, Mandrake 8.2,=20 Debian ?.? and SunOS 5.8 with gcc. It is still quite broken for=20 Sun's compiler. (It finally compiles, but fails most tests, and=20 hangs during t_htdig.) What other platforms need testing? RedHat and OS X are definites. (RedHat on the compile farm doesn't seem to have Apache, which is=20 needed for make check. Also, I don't want to use it for big digs.) Does anyone have access to Cygwin? SuSE? Non-x86 Linux? I've incorporated a patch, based on Richard Monroe's excellent sketch,=20 to use -Wno-deprecated when needed. Jesse, Sun's cc also had problems with select, but in the main=20 directory so it's probably just a coincidence. Finally, I still haven't got autoconf working, so most of the=20 changes I made manually at "all levels" (configure, configure.in,=20 aclocal.m4, acinclude.m4, etc.). Before the 3.2.0b5 is released,=20 we'll have to make sure the automatic process works... Cheers, Lachlan On Sun, 18 May 2003 00:32, J.E.J. op den Brouw wrote: > There is a ./configure issue on HP-UX 10.20 about > select(2) not found in de db tree. |
Thanks for helping keep SourceForge clean.
X