I would have liked to do it, but there's no way I
could volunteer for this weekend (a few family things
popped up with my Dad in the hospital and my
Uncle/Godfather passing away)... But my comments
about 2.2.1 are:
1. I think the proxy fixes should be part of 2.2.1,
but I think that, especially now with all the
revisions that we worked through in trunk,
they require more testing. So maybe a coupla
extra days would be nice.
2. Monday is a holiday for many US companies.
So timing might be an issue.
3. Showstoppers exist, but I haven't had time to
investigate them, but we can't ignore them :)
On Jan 12, 2006, at 3:57 PM, William A. Rowe, Jr. wrote:
I'm offering to RM this package late friday or sometime Saturday if
there's
no serious objection. Fixing or not fixing partial page results is
obviously
not a regression, although I'm happy to wait an extra couple days
if the fix
has been agreed upon, committed and is only undergoing some extra
bashing-upon.
Part of the Win32 binaries issue is that the -src.zip still
required too much
tweaking to be called the official version, by the time i'd
finished build/test
I'd had to make too many other 'minor tweaks'. I'd feel much
warmer releasing
2.2.1 as binaries on Win32, as the build system (now) corresponds
to the actual
product.
I can do one of three things to eliminate awk for generating .rc
files;
* use one common module .rc file with some /D inputs for module
name, etc.
* create the dozens of .rc files in svn
* have the buildconf create all the .rc files
I'm leaning twords the first option.
Bill
