I noticed that https://issues.apache.org/jira/browse/TEZ-3860 is present in 0.9 branch but not part of 0.10.0. Is this intentional? TEZ-4223 is dependent on TEZ-3860, if we do not want this in 0.10.0 we can skip TEZ-4223.
On Tue, Aug 11, 2020 at 7:09 PM Harish Jai Prakash Perumal <[email protected]> wrote: > This is also a regression and would be good to have: > https://issues.apache.org/jira/browse/TEZ-4223 > > On Tue, Aug 11, 2020 at 2:14 PM Rajesh Balamohan <[email protected]> > wrote: > >> It would be good to add the following tickets >> >> https://issues.apache.org/jira/browse/TEZ-4208 >> https://issues.apache.org/jira/browse/TEZ-3645 >> https://issues.apache.org/jira/browse/TEZ-4216 >> https://issues.apache.org/jira/browse/TEZ-4199 >> >> >> ~Rajesh.B >> >> On Tue, Aug 11, 2020 at 1:14 PM László Bodor <[email protected]> >> wrote: >> >> > Hi! >> > >> > JIRAS NEEDED: >> > 1 known open regression at the moment, which (I'm aware of and) might be >> > worth waiting for: https://issues.apache.org/jira/browse/TEZ-4213 >> > >> > RELEASE MANAGER: >> > I'm interested in doing this! >> > >> > Regards, >> > Laszlo Bodor >> > >> > On Mon, 10 Aug 2020 at 16:17, Jonathan Eagles <[email protected]> >> wrote: >> > >> > > JIRAS NEEDED >> > > Please give feedback for Tez 0.10.0 release planning. Specifically, >> let's >> > > propose jiras required for the release as well as the timing for the >> > > release. Let's keep this discussion open for the week and reply with >> JIRA >> > > proposals. >> > > >> > > RELEASE MANAGER >> > > If anyone is wanting to volunteer for 0.10.0 release manager, please >> let >> > me >> > > know. The process is documented, but having someone walk through the >> > > process the first time is best. >> > > >> > > Jon Eagles >> > > Tez PMC Chair >> > > >> > >> >
