> Please don't take any of my comments as overly critical or flaming. > You're new to the project and attempting to take on some heavy > lifting--so I'm trying to transfer some experience.
Of course not. Let me clarify a bit: My previous post with the proposed schedule could be restated with the releases as 3.2beta4, 3.2beta5, 3.2beta6 etc. I guess it comes down to that I think the code is good enough now to consider a release in the near-term without a raft of changes/improvements. The need for a release PDQ is a result of Gilles level of frustration with 3.1.x. I also think a case could be made for a release with some of the things on your list along with the zlib-WordDB-compression and a improved inverted index representation in the WordDB to cut out the excessive number of rows in the WordDB. If we accomplish that, then it gets some of the pressure off to merge with Mifluz 0.23 to fix bugs. The combination of the two would offset any WordDB size increase penalty from using zlib page-compression. If a short-term need for a release isn't warranted, then as long as we stagger some of these features into a schedule by priority... it sounds good. Let's just get a schedule of deliverables for either a sequence of 3.2betaX or a sequence of releases. For task organization and morale this could be useful. So Gilles, is there a short-term need for a release without some of the larger things on the TODO list? Thanks! Neal Richter Knowledgebase Developer RightNow Technologies, Inc. Customer Service for Every Web Site Office: 406-522-1485 ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
