Thanks for bringing this up Jan. My understanding is that that removal can only happen if an API has been deprecated for at least a major version; i.e. a deprecation added in 2.0.1 has to wait till 4.0.0 for removal and no sooner.
Thanks, S On Tue, Apr 23, 2019 at 8:17 AM Jan Hentschel < [email protected]> wrote: > Hi everyone, > > in the PR for HBASE-22262<https://github.com/apache/hbase/pull/162> we > noticed that there could be easily a misunderstanding on when to remove > deprecated methods. In the book< > http://hbase.apache.org/book.html#hbase.versioning.post10> it is > documented “an API needs to be deprecated for a major version before we > will change/remove it.”. As the discussion on the PR shows it leaves some > room for interpretation and should be made more specific, including some > examples. I think we all agree that removing a method in 3.0.0 is ok when > it was deprecated back in 2.0.0, but what do we do with methods or classes > which were deprecated in a minor or patch version? As an example, if we > deprecate a method in 2.3.0, should it be removed in 3.0.0 or 4.0.0? > > Best, Jan >
