+1 for the approach. I think there are some critical JIRA for 4.3 and not all
of them are committed. I will mark them for 4.3 release.
Thanks,
On Friday, July 15, 2016 12:06 PM, Rohini Palaniswamy
<[email protected]> wrote:
It should be fine changing java version in 4.3. Pig to 0.16 should also be
fine. Those two I can vouch with confidence. We were running with Java 7 for
about two years and now have been running with Java 8 for more than a year. So
jdk upgrade does not need baking time. Openjpa and curator I am fine with
deferring. For httpclient, shouldn't we upgrade if it is a security issue?
We need to create version 4.3 and mark all closed ones with trunk as 4.3.
Anything in patch available that we are going to incorporate mark for 4.3 and
rest leave it as it is. That will make it easy to scrub and scope the release.
If anyone specifically comes back asking for things not marked for 4.3, then we
can pull them into 4.3. For the ones in Patch Available, we can divide the
review work and get all in within 2 weeks.
Regards,Rohini
From: Robert Kanter <[email protected]>
To: "[email protected]" <[email protected]>; Rohini Palaniswamy
<[email protected]>; Purshotam Shah <[email protected]>; Satish
Subhashrao Saley <[email protected]>
Sent: Friday, July 15, 2016 11:31 AM
Subject: Re: [SCOPE] Oozie 4.3.0 Release
I don't think we have any guidelines defined anywhere about when it's okay to
change the minimum Java version, but perhaps we need to wait until the next
major release (5.0)? That said, Hadoop did this in a minor release and Java 6
was EoL in 2013. So I'm fine with doing it in 4.3 if nobody has an objections;
we should just make sure to call that out in our release notes.
Otherwise, nothing comes to mind for anything we should leave out other than
the Oozie on Yarn stuff, which is not currently in trunk anyway.
I know there's a number of Spark Action JIRAs; we should make sure to include
all of these and any pending ones. @Rohini, @Puru, @Satish, anything you think
needs more time to bake that we should hold off on including in the release?
thanks- Robert
On Fri, Jul 15, 2016 at 8:35 AM, Abhishek Bafna <[email protected]> wrote:
Hi All,
Any suggestions or comments on the scope for the release?
Thanks,
Abhishek
> On Jul 13, 2016, at 3:07 AM, Abhishek Bafna <[email protected]> wrote:
>
> Hi All,
>
> Oozie is starting the release process for Oozie 4.3.0. This thread is for
> discussion about the scope of the release. Please provide your suggestion
> about what should be included (or any exclusions) in the release.
>
> Currently, we have around 158 patches submitted to trunk. Based on the scope,
> we will include (exclude) more if required.
> Version Upgrade
> Java 1.7 (OOZIE-2036 <https://issues.apache.org/jira/browse/OOZIE-2036>)
> OpenJPA (OOZIE-2488 <https://issues.apache.org/jira/browse/OOZIE-2488>),
> Curator (OOZIE-2231 <https://issues.apache.org/jira/browse/OOZIE-2231>),
> HttpClient (OOZIE-2538 <https://issues.apache.org/jira/browse/OOZIE-2538>),
> Pig (OOZIE-2602 <https://issues.apache.org/jira/browse/OOZIE-2602>).
> New Features/Improvements: Add default JT and NN, Database schema service
> check, instrumental metrics, Tomcat upgrade etc.
> Bug Fixes.
> Provide your opinion on inclusion/exclusion of the above points or more for
> the scope of the release. We can also, take some work which is already done
> and review is pending for them (depending on the availability of the
> reviewers).
>
> Thanks,
> Abhishek
