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: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- 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 [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
