https://issues.apache.org/jira/browse/TEZ-2798 and https://issues.apache.org/jira/browse/TEZ-2815 should be blockers for this. Even though the APIs may be marked unstable, having them throw exceptions in their signature is essential. Also, without these there is currently a constant stream of NPE's in all tests that use the MockDAGAppMaster.
Bikas -----Original Message----- From: Hitesh Shah [mailto:[email protected]] Sent: Friday, December 4, 2015 11:04 AM To: [email protected] Subject: Re: [DISCUSS] Next release from the 0.8 line - 0.8.2 +1 to the 0.8.2 release with a couple of caveats: 1) Unit tests have been very flaky recently on Jenkins and we should aim to get them stable before releasing 2) Clearly calling out the pluggable service APIs as unstable/likely to change within the 0.8.x line as part of the release notes. - Hitesh On Dec 3, 2015, at 1:24 PM, Siddharth Seth <[email protected]> wrote: > More than 50 jiras have been added since the last release from the 0.8 > line (0.8.1-alpha). More importantly, this branch has gotten quite a > bit of testing, especially while running against Hive 2.0 and LLAP. > At this point, I think we can drop the alpha monicker from the release > - and mark it for public consumption. The APIs for pluggable services > can be called out as unstable in the release notes. > > Thanks > - Sid
