It's becoming clear that many users effectively ignore deprecation warnings. I think we may need to do something here.
First, I don't think we can be too critical of users for this. I'm not sure we've been clear enough of exactly what deprecation means or how to deal with it, and for plugin authors it's even more confusing. I wonder if we could formalise our strategy soon after 1.0 to achieve the following: • Encourage users to move away from deprecated API as soon as they can so we don't get an influx when the item is removed • Make it clear what the compatibility implications of a deprecation are (e.g. when will the deprecated item go away, what's the backwards compatibility story) • Establish boundaries for version compatibility to help plugin authors Not saying we need to do anything now, but worth mulling over until the time when we do. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
