Re: [DISCUSS] Tez 0.10.0 Release Planning

[László Bodor <bo...@gmail.com>]

FYI: there are 2 issues which block 0.10.0 release, and I'm working on
these below:
https://issues.apache.org/jira/browse/TEZ-4228 -> ready to merge
https://issues.apache.org/jira/browse/HIVE-24111 -> hang in hive unit test,
need to confirm if it's a tez or hive bug (if Hive, I'll proceed with tez
RC immediately)

note: HIVE-24111 was also discovered after tez 0.9.1->0.9.2 upgrade
earlier, so it should be considered while doing 0.9.x release (see thread
in tez dev list: "Failed Hive upgrade to Tez 0.9.2")
"

On Thu, 27 Aug 2020 at 15:18, László Bodor <bo...@gmail.com>
wrote:

> I've made branch-0.10.0 point to current master, which contains all the
> patches mentioned in this thread, I'm about to start the release process.
>
> On Tue, 25 Aug 2020 at 16:33, Jonathan Eagles <je...@gmail.com> wrote:
>
>> This will be a necessary step for this release. The bulk update option
>> (found under the tools) will be a great idea to address this.
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20TEZ%20AND%20resolution%20!%3D%20null%20and%20fixVersion%20in%20(0.10.1)
>>
>> Because of the initial attempt at 0.10.0, the step to create a branch
>> release will need some unique steps. We will need to re-branch for 0.10.0
>> (delete branch and then create new or perhaps upmerge 0.10.0 from master).
>>
>> On Tue, Aug 25, 2020 at 9:10 AM László Bodor <bo...@gmail.com>
>> wrote:
>>
>> > ~60 jiras contain 0.10.1 as fixVersion, with a bulk update I can refresh
>> > them to 0.10.0 in order to stay inline with the current release.
>> >
>> > On Tue, 25 Aug 2020 at 16:07, Jonathan Eagles <je...@gmail.com>
>> wrote:
>> >
>> > > There was some initial work on a 0.10.0 release so there are some or
>> > > perhaps many JIRAs should be retargeted from 0.10.1 to 0.10.0.
>> > >
>> > > On Tue, Aug 25, 2020 at 7:03 AM László Bodor <
>> bodorlaszlo0202@gmail.com>
>> > > wrote:
>> > >
>> > > > There is only 1 jira left before release (TEZ-3645), I think we can
>> > wait
>> > > > for it to be committed (this week).
>> > > > We consistently used 0.10.1 as fixVersion on tickets, I guess all
>> > > > occurrences should be fixed to 0.10.0 on resolved tickets, as we are
>> > > about
>> > > > to release 0.10.0 now.
>> > > >
>> > > > Regards,
>> > > > Laszlo Bodor
>> > > >
>> > > >
>> > > > On Sun, 16 Aug 2020 at 09:54, László Bodor <
>> bodorlaszlo0202@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Applied "0.10_blocker" label to opened and mentioned jiras.
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/browse/TEZ-4213?jql=project%20in%20(%22Apache%20Tez%22)%20and%20labels%20%3D%200.10_blocker%20and%20status%20not%20in%20(Closed%2C%20Resolved)
>> > > > >
>> > > > > Regards,
>> > > > > Laszlo Bodor
>> > > > >
>> > > > >
>> > > > > On Fri, 14 Aug 2020 at 16:48, Jonathan Eagles <je...@gmail.com>
>> > > wrote:
>> > > > >
>> > > > >> I think there is an outdated branch-0.10.0 from an early attempt
>> at
>> > a
>> > > > >> 0.10.0 release. This branch should be recut or updated to be
>> > identical
>> > > > to
>> > > > >> the main branch.
>> > > > >>
>> > > > >> On Thu, Aug 13, 2020 at 12:44 AM Harish Jai Prakash Perumal
>> > > > >> <hj...@cloudera.com.invalid> wrote:
>> > > > >>
>> > > > >> > 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 <
>> > > > >> > hjp@cloudera.com>
>> > > > >> > 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 <
>> > > > >> rbalamohan@apache.org>
>> > > > >> > > 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 <
>> > > > >> bodorlaszlo0202@gmail.com
>> > > > >> > >
>> > > > >> > >> 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 <
>> > > jeagles@gmail.com
>> > > > >
>> > > > >> > >> 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
>> > > > >> > >> > >
>> > > > >> > >> >
>> > > > >> > >>
>> > > > >> > >
>> > > > >> >
>> > > > >>
>> > > > >
>> > > >
>> > >
>> >
>>
>