I'd refer to it as an incompatible change; we expressly label the annotations as IA.Public.
If you think it's too late to get in for 3.0, I can make a jira and put it on the back burner for when trunk goes to 4.0? On Fri, Sep 22, 2017 at 12:49 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: > Is this itself an incompatible change? I imagine the bytecode will be > different. > > I think we're too late to do this for beta1 given that I want to cut an > RC0 today. > > On Fri, Sep 22, 2017 at 7:03 AM, Sean Busbey <bus...@cloudera.com> wrote: > >> When Apache Yetus formed, it started with several key pieces of Hadoop >> that >> looked reusable. In addition to our contribution testing infra, the >> project >> also stood up a version of our audience annotations for delineating the >> public facing API[1]. >> >> I recently got the Apache HBase community onto the Yetus version of those >> annotations rather than their internal fork of the Hadoop ones[2]. It >> wasn't pretty, mostly a lot of blind sed followed by spot checking and >> reliance on automated tests. >> >> What do folks think about making the jump ourselves? I'd be happy to work >> through things, either as one unreviewable monster or per-module >> transitions (though a piece-meal approach might complicate our javadoc >> situation). >> >> >> [1]: http://yetus.apache.org/documentation/0.5.0/interface-classi >> fication/ >> [2]: https://issues.apache.org/jira/browse/HBASE-17823 >> >> -- >> busbey >> > > -- busbey
