14 Jan
2011
14 Jan
'11
9:06 a.m.
Hi Sergiu,
I'd like to discuss this point that you've made in some other mail:
"Velocity 1.7, which brings many new features and improvements, but breaks a lot of
velocity macros (still working on fixing the broken code)"
Does this mean users who have existing scripts will have things not working anymore? (I
guess so if we have broken stuff on our side)
If so, what can we do to make them suffer less when upgrading? Can we start by listing
broken stuff here and add them to the release notes?
Thanks
-Vincent