Re: [infinispan-dev] API stability policy for major vs minor vs patch releases

It's the result of https://issues.jboss.org/browse/ISPN-925 and http://goo.gl/MUJaK I think it was an oversight. I agree that it should have been deprecated and removed in Infinispan 6.0. I've created a JIRA to restore it and mark it as deprecated: https://issues.jboss.org/browse/ISPN-953 On Feb 23, 2011, at 6:00 PM, Paul Ferraro wrote: > In my course of upgrading AS6 from 4.2.0.Final to 4.2.1.CR3, I came > across a NoSuchMethodError. Specifically, a couple AS components > utilize DistributionManager.isLocal(String), which was dropped from the > public API sometime after 4.2.1.CR1. > > While the fix is trivial enough (in the end I'll need to perform several > component release to compensate), this raises the larger issue of a API > stability policy for major vs minor vs patch releases. At the very > least, I don't think its wise to remove methods from a public interface > in a patch release. In my opinion, removing methods from a public API > should only happen across major releases, and even then, only after > being formally deprecated. > > Thoughts? > > Paul > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev