On 9/24/2014 3:45 PM, Todd W Lainhart wrote: > Is there a policy regarding when deprecated APIs are finally removed from > subsequent distributions? > > E.G. If I find a field marked as @deprecated as of 4.2, when would I > expect it to get pulled, if at all? Or is the policy not to expect any > further development (e.g. bug fixes) for deprecated API? Perhaps a bit of > both?
I am curious about this as well, but I think I know at least part of the answer. It's probably the same as Lucene/Solr, which is a fellow Apache project to HttpComponents. On Lucene/Solr, deprecations on one major release get removed from the next major release. For Lucene/Solr, the first number in the version refers to the major release. In real terms, things that are currently being deprecated in 4.x releases on that project will be completely removed from the 5.0 release, when it happens. If I'm right in my general assessment, this is an important question: Does the HttpComponents project consider 4.4 to be the next major release, or 5.0? Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
