Hi,
Just to be clear. VelocityServlet should absolutely stay in the core until
a 2.0 release. There's no reason to break any existing applications by
taking it out. (And I'm sure there are applications written 3 years ago
using Velocity that are still running).
There's no downside to leaving it in, except a little bit of cruft in the
jar file. Once 1.5 is released there will be no new VelocityServlet users.
VelocityServlet is deprecated in the Javadocs. The "webapps" page on the
web site suggests other approaches (and mentions VelocityServlet is
deprecated). All examples have been removed. Hence support costs are nil.
WILL
----- Original Message -----
From: "Tim Colson (tcolson)" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <velocity-dev@jakarta.apache.org>
Sent: Tuesday, September 27, 2005 11:37 AM
Subject: RE: Versioning guidelines and ABI compability
beneficial to release 1.5.1, 1.5.2, etc every couple of
I'd suggest point releases "when they make sense"... criteria to be
determined on the list.
version called "1.5.0" may discourage users. Why not just
start with "1.5"?
1.5, 1.5.1, 1.5.2 is fine with me.
Re: deprecation. My opinion - anything that's commonly used (e.g.
VelocityServlet) should stay in for the entire lifecycle of
the "major" [release number].
Hmm... I dunno, maybe this isn't a great example because VS causes pain
(imho) for newbies who should be using VVS in Tools. But I'd hate to see
it linger on for 1.5, 1.6, 1.7... and on and on until 2.0. Depends on
how often the major number increments.
But it does seem like Velocity is due soon for a 2.0 release. Heck, 1.x
makes -some- people nervous. ;-)
-Timo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
