At 10:51 AM +0100 12/6/99, [EMAIL PROTECTED] wrote: >I just saw that the integration of the new compression code is >submitted to a vote. So I won't continue commiting before it's ok! Yes, the 3-2-x tree is under feature-freeze, which means anything except bug-fixes must be submitted for a vote. >It is fully functional and I have tested it in several configurations >and large indexes. It has an auto-test feature, that when enabled >checks if each page it compresses can be decompressed back to the >original. This obviously sounds good. >Concerning HtVectorGeneric: My code relies on this, but >HtVectorGeneric hasn't been checked/reviewed so as to be fully >functional. The features I use work fine, but it certainly needs some >attention before everybody starts using it. ... >What I suggest is to integrate the compression in this version of >htdig (so my vote is yes), to commit the HtVectorGeneric, but that >people avoid using it before I double check it. (probably next week) I'm a bit confused here. Avoid using HtVectorGeneric? Fine. Avoid using the rest of the code until you finish checking it? Not so good, obviously. Assuming you mean that testing on the compression can begin now, my vote is +1. If you're saying we can't test until next week, I'd like a bit more explanation why. (It's not that I'm worried, but I'd like to kill off remaining bugs and get this out sooner rather than later.) -Geoff ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
