Re: [DISCUSS] moving to Apache Yetus Audience Annotations

2017-09-22 Thread Andrew Wang
Yea, unfortunately I'd say backburner it. This would have been perfect during alpha. On Fri, Sep 22, 2017 at 11:14 AM, Sean Busbey wrote: > 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

Re: [DISCUSS] moving to Apache Yetus Audience Annotations

2017-09-22 Thread Sean Busbey
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 wrote: > Is this itself an incompat

Re: [DISCUSS] moving to Apache Yetus Audience Annotations

2017-09-22 Thread Andrew Wang
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 wrote: > When Apache Yetus formed, it started with several key pieces of Hadoop that >

[DISCUSS] moving to Apache Yetus Audience Annotations

2017-09-22 Thread Sean Busbey
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 Y