Argh. a) sorry, too late. b) no one ever confirmed my fix for VELOCITY-718, so i never merged it into the 1.6.x branch c) while waiting for confirmation, i forgot about 718, so i didn't even remember it when i asked for 748 to be filed. d) i'm apparently doing too much if i can't even keep track of a critical threading bug.
ok, i'm done whining. at this point, i'm ready to just assume (yikes!) that my fix for 718 works, and merge it into the 1.6.x branch and begin working on a 1.6.4 release. considering impending holiday offline periods, the odds of 1.6.4 coming out in 2009 are not promising. 2009/12/16 Jarkko Viinamäki-2 <w...@sci.fi>: > > -1 No, if critical bugfix VELOCITY-718 is not included as well. If it is, +1. > > -- > View this message in context: > http://old.nabble.com/-VOTE--Release-Velocity-Engine-1.6.3-tp26751238p26809833.html > Sent from the Velocity - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org