Hi,
Some thoughts after a little more AM coffee.
Re: major/minor/patch versions. Once 1.5 is released I'd like
to do more frequent releases with bug fixes. It's frustrating for users to
report a bug and hear "this is fixed but not released". I think it'd be
beneficial to release 1.5.1, 1.5.2, etc every couple of months. I agree a
version called "1.5.0" may discourage users. Why not just start with "1.5"?
Of course, once we fix the 37 issues remaining in the 1.5 release we might
found out that there are no bugs left. :-)
Re: deprecation. My opinion - anything that's commonly used (e.g.
VelocityServlet) should stay in for the entire lifecycle of the "major"
patch. The stability of the Velocity API is definitely a strong point.
When an application has a dozen different libraries, even a small change to
an API is a pain.
I'm ok for removing small deprecated API changes after 2 versions as Henning
suggests if they are uncommon use cases. (Geir may disagree).
Best,
WILL
----- Original Message -----
From: "Tim Colson (tcolson)" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[email protected]>
Sent: Tuesday, September 27, 2005 8:54 AM
Subject: RE: Versioning guidelines and ABI compability
i meant dep in 1.0, leave in 1.1, remove in 1.2
Ok, then I'm solid +1
major versions shouldn't care about B.C. patches shouldn't mess with
anything more than they have to.
+1
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]
