I'd like to create the RC early next week - ideally Monday. The following issues are still pending, which are either patch available or trivial fixes. https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20%22Target%20Version%2Fs%22%20%3D%200.8.2
Once these go in, I'll create an RC. Thanks - Sid On Fri, Dec 11, 2015 at 3:45 PM, Bikas Saha <[email protected]> wrote: > I am planning to pull in https://issues.apache.org/jira/browse/TEZ-2633 as > it allows vertex managers (specially shuffle) to correctly distinguish > attempt retries. This prevents incorrect double counting etc. for > stats/slow > start etc. It includes API changes on the VertexManagerPlugin and > VertexManagerPluginContext but retains the older APIs and hence > compatibility will be maintained with existing code. After this, I can also > pull in https://issues.apache.org/jira/browse/TEZ-2943 into branch-0.7. > > Please let me know if there are any concerns. > Bikas > > -----Original Message----- > From: Jianfeng (Jeff) Zhang [mailto:[email protected]] > Sent: Thursday, December 10, 2015 9:08 PM > To: [email protected] > Subject: Re: [DISCUSS] Next release from the 0.8 line - 0.8.2 > > > Create umbrella ticket for flaky test > > https://issues.apache.org/jira/browse/TEZ-2989 > > > > Best Regard, > Jeff Zhang > > > > > > On 12/8/15, 2:52 PM, "Siddharth Seth" <[email protected]> wrote: > > >Thanks for the responses. I'll take a look at what is required for > >TEZ-2815 > >and TEZ-2798. Hitesh, do you have specific jiras in mind for the flakey > >tests. There's a couple more jiras which I'd like to get in - will send > >out a list with a 0.8.2 target soon. > > > >On Fri, Dec 4, 2015 at 12:00 PM, Bikas Saha <[email protected]> wrote: > > > >> 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 > >> > >> > >> > > >
