Sean Legassick wrote:
>
> No, this is a very useful service. I guess I read Jon's message
> as "look Gump says the turbine build was failing, somebody fix
> it" - whereas actually it was saying "heads up, log4j have just
> changed their API and next time they release we'll need to
> change our code to build against the new release".
Don't just simply be a victim. If somebody changes an interface that you
depend on, seek them out and educate them on the necessity of maintaining
some level of backwards compatibility for a release or so on behalf of your
customers.
Once projects start respecting their published contracts, I'm hoping that
projects start asking for notification of deprecation warnings.
- Sam Ruby
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
