-0 non-binding
We use it and haven't had any troubles with it so far. So no real
reasons to submit bugs. Although we are still running in 1.4.17 and we
haven't tried 1.5 yet.
Moving it would add an extra migration step and we are afraid of it not
being supported any longer.
However putting it somewhere where we can find it and keep using it
would be an option, although not one we prefer above it being part of
wicket itself.
Thijs
On 6/15/11 11:06 PM, Maarten Bosteels wrote:
We are planning to use wicket-velocity and we will post bugs when we find
them ;-)
I would prefer if it stayed where it is now and follows the same release
cycle as wicket core.
Non binding of course.
Maarten
On Wed, Jun 15, 2011 at 10:43 PM, James Carman
<[email protected]>wrote:
On Wed, Jun 15, 2011 at 4:40 PM, Martin Grigorov<[email protected]>
wrote:
Should we wait 72 hours for the vote or I can move it tomorrow ?
What was Martijn's official vote? If it was -1, that's a veto. Code
modifications (which this would be) can be vetoed.
