> Well, there haven't been many flame wars around here recently, so let me
> start one. I seem to be good at that. :-)
>
> What I propose is that we take this document (or one similar to it) and
> migrate it up to the overall Jakarta Project instead of just being a
Turbine
> policy and get all the projects to "sign" their name on it.
>
> <http://jakarta.apache.org/turbine/deprecation.html>
>
> I think it would go a long way towards raising awareness of the need to
> deprecate things (thanks to Sam starting this with Gump) as well as make
the
> corporate types feel more comfortable with regards to depending on "that
> Open Source Software stuff"...
>
> Comments?
+1.
My only comment : you should always be allowed any API change when you
change the major revision number, without a deprecation phase (for example,
I think it's ok if version 2.0, immediately following version 1.62, has a
different API).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
