Re: [SCOPE] Oozie 4.3.0 Release

Hi All, All the 4.3.0 release marked jiras are completed. Release candidate tag is created and pushed. Now working on creating release artifacts. Regards, Abhishek > On Oct 19, 2016, at 9:28 PM, Abhishek Bafna wrote: > > Hi All, > > Currently we have three Oozie Blocker

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, Currently we have three Oozie Blocker issues marked for 4.3.0 release. OOZIE-2621 OOZIE-2705 OOZIE-2710 Robert, Rohini, Jaydeep, Purshotam : Would it be possible to review these them. Regards, Abhishek > On Oct 11, 2016, at 7:42 AM, Abhishek Bafna wrote: > > Hi

Re: [SCOPE] Oozie 4.3.0 Release

Hi Robert, OOZIE-2658 has been rebased and OOZIE-2613 is also ready with the discussed workaround in the issue thread. Keeping those for 4.3 and moving all the others. Thanks, Abhishek > On Oct 8, 2016, at 5:01 AM, Robert Kanter wrote: > > - I took care of OOZIE-1814

Re: [SCOPE] Oozie 4.3.0 Release

- I took care of OOZIE-1814 yesterday. - OOZIE-2658 should be good after it gets rebased (doesn't apply cleanly); I'm guessing that will have to wait until Monday PDT due to timezones. - I'm not sure what's the current status of OOZIE-2613. test-patch looks like it's ready, but from subsequent

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, Today EOD (UTC), we will freeze the scope and further commits into branch-4.3 expect any blocker issues. By early next week, we will have our first release candidate for review. Regards, Abhishek > On Sep 23, 2016, at 11:11 PM, Abhishek Bafna wrote: > > Hi All,

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, The new branch creation and update of the version in the current branch will be done on Monday (IST). Thanks, Abhishek > On Sep 21, 2016, at 10:56 PM, Robert Kanter wrote: > > --94eb2c04982ae57b7b053d07d72b > Content-Type: text/plain; charset=UTF-8 > > Oh,

Re: [SCOPE] Oozie 4.3.0 Release

Oh, right. I forgot that Shwetha was going to help you with that. That's fine with me. On Wed, Sep 21, 2016 at 3:22 AM, Abhishek Bafna wrote: > Hello Robert, > > Yes. I do not have permissions to do it. I was planning to take Shwetha's > help. I am fine with you doing

Re: [SCOPE] Oozie 4.3.0 Release

Hello Robert, Yes. I do not have permissions to do it. I was planning to take Shwetha's help. I am fine with you doing it. Please let me know if there is any change in the plan. Thanks, Abhishek > On Sep 21, 2016, at 2:11 AM, Robert Kanter wrote: > > Abhishek, > > You

Re: [SCOPE] Oozie 4.3.0 Release

Abhishek, You don't have git permissions to create the release branch. I can take care of that on Thursday if you want. - Robert On Tue, Sep 20, 2016 at 1:30 PM, Abhishek Bafna wrote: > Hello All, > > I think we can create the new branch by Thursday (IST) and update

Re: [SCOPE] Oozie 4.3.0 Release

Hello All, I think we can create the new branch by Thursday (IST) and update version for new branch and master. If we have any important pending Jira's by then we will commit them to both new branch and master. I will start working on the next steps for release from release doc.

Re: [SCOPE] Oozie 4.3.0 Release

Sorry Abhishek for the long delay. Was on vacation and then busy catching up with stuff. I did review a bunch of patches today which were marked 4.3.0 and Patch Available apart from those which Robert or others have already not commented on. Skipping those as they have better context. Tag my name

Re: [SCOPE] Oozie 4.3.0 Release

Hello Robert, Rohini, Purshotam, Jaydeep As we discussed earlier, will be bumping the priority of some Jira's to 'blocker' for to be included into Oozie 4.3.0 release. We will try to complete as much possible out of that. (It would to good complete all.) @All, If I miss something, Please do

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, It has been a long time since we started the scope discussion for the Oozie-4.3.0 release. Since then a lot of patches got reviewed and committed and I would to thank each one you for contributing your efforts for that. I think we should move to the next stage and go into blocker only

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, Can we please look into these upgrade related bugs? ActiveMQhttps://issues.apache.org/jira/browse/OOZIE-2552 HttpClient https://issues.apache.org/jira/browse/OOZIE-2538 OpenJPA https://issues.apache.org/jira/browse/OOZIE-2488 Curator

Re: [SCOPE] Oozie 4.3.0 Release

Hello All, How is it looking now? I think we should move to blocker and critical patch mode. If required, we can take couple of days extra there. ~Abhishek > On Aug 19, 2016, at 11:31 AM, Abhishek Bafna wrote: > > Sure Robert. We can use some more time. > > ~Abhishek

Re: [SCOPE] Oozie 4.3.0 Release

Sure Robert. We can use some more time. ~Abhishek > On Aug 19, 2016, at 7:13 AM, Robert Kanter wrote: > > Do you think we could wait one more week? I've been really hammered with > some other work and there's more that I'd like to review here that I > haven't been able to

Re: [SCOPE] Oozie 4.3.0 Release

Sure. I guess we can one extra week and complete some more work. Thanks everyone for responding. ~Abhishek > On Aug 12, 2016, at 2:46 PM, Purshotam Shah > wrote: > > Yes. I also have some pending patches. > >On Friday, August 12, 2016 2:11 AM, Robert

Re: [SCOPE] Oozie 4.3.0 Release

Yes. I also have some pending patches. On Friday, August 12, 2016 2:11 AM, Robert Kanter wrote: Ya, I could use some more time as well.  I have some deadlines early next week, which has kept me from doing more reviews. thanks - Robert On Thu, Aug 11, 2016 at

Re: [SCOPE] Oozie 4.3.0 Release

Ya, I could use some more time as well. I have some deadlines early next week, which has kept me from doing more reviews. thanks - Robert On Thu, Aug 11, 2016 at 11:04 AM, jaydeep vishwakarma < jaydeepma...@gmail.com> wrote: > Let see if we can wait for another week. So we can merge few more

Re: [SCOPE] Oozie 4.3.0 Release

Let see if we can wait for another week. So we can merge few more important jiras. Few of them I personally want to get reviewed and merged. Regards, Jaydeep On Thu, Aug 11, 2016 at 4:09 PM, Abhishek Bafna wrote: > As previously discussed, we will be moving with whatever

Re: [SCOPE] Oozie 4.3.0 Release

As previously discussed, we will be moving with whatever patches can be reviewed/merged till end of this week. But there are some which needs to be reviewed and merged, mainly regarding the upgrades. Some of the patches require Java 1.7, so I think we should review OOZIE-2036 and merged it.

Re: [SCOPE] Oozie 4.3.0 Release

Cleaned up that list and now no jira refers to "trunk". Patch Available jiras targeted for trunk now point to 4.4.0. https://issues.apache.org/jira/issues/?jql=project%20%3D%20Oozie%20AND%20fixVersion%20%3D%204.3.0%20and%20status%20%3D%20%22Patch%20Available%22%20ORDER%20BY%20status%20DESC

Re: [SCOPE] Oozie 4.3.0 Release

Ya, let's unset those remaining open trunk ones. I agree, we need to put in some effort to clean out old JIRAs and to review Patch Available JIRAs. Also, I just created OOZIE-2625 to drop workflowgenerator. We can discuss the issue more there, but I listed a few reasons on OOZIE-2625 about why.

Re: [SCOPE] Oozie 4.3.0 Release

https://issues.apache.org/jira/issues/?jql=project%20%3D%20Oozie%20AND%20fixVersion%3D%20%22trunk%22%20and%20status%20%3D%20open%20ORDER%20BY%20resolution%20ASC%2C%20status%20DESC=50 These are jiras open and marked trunk. Should we unset fix version on these or mark them for next release? Don't

Re: [SCOPE] Oozie 4.3.0 Release

I think it would be better to send out email for the bulk change. If there are any issues or jiras wrongly marked someone can respond. We do that with Pig and there are always couple of jiras that folks come back with feedback on pulling back to release. On Wed, Aug 3, 2016 at 8:07 AM, Robert

Re: [SCOPE] Oozie 4.3.0 Release

Abhishek, next time you do a bulk change, please remember to tell it not to send out an email for every change :) On Tue, Aug 2, 2016 at 4:28 PM, Robert Kanter wrote: > Rohini, that sounds good to me. Especially because we're on "master" > branch but "trunk" version in

Re: [SCOPE] Oozie 4.3.0 Release

Rohini, that sounds good to me. Especially because we're on "master" branch but "trunk" version in JIRA and it gets a little confusing. Instead of deleting "trunk", I think we're better off just renaming it to the release number. Otherwise, we'll have to re-label any current "trunk" fields. We

Re: [SCOPE] Oozie 4.3.0 Release

I also did mark some of the enhancement jiras that Satish was working on and which might take time to review to 4.4.0 Regards, Rohini On Tue, Aug 2, 2016 at 3:01 PM, Rohini Palaniswamy wrote: > Abhishek, > Can you mark all jiras already committed to trunk as 4.3.0

Re: [SCOPE] Oozie 4.3.0 Release

Abhishek, Can you mark all jiras already committed to trunk as 4.3.0 and those planned in the scope document as 4.3.0? This will help filter on those and review instead of referring to a google doc. I can pick up 10-15 jiras for review end of this week. We should try to get majority of patches

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, As we prepared a Oozie 4.3.0 scope document and listed all the things which we wanted to include in the release. In the last few days, I spent some time and reviewed some of

Re: [SCOPE] Oozie 4.3.0 Release

Hi, I looked into the available patches and prepared the list. I have put, scope content which we have discussed till now, into a word document. (For the better formatting and easy to read and comment). I have noted the additional Jira into the list. Added two more Jira related to spark

Re: [SCOPE] Oozie 4.3.0 Release

That list looks good to me. The only one I'm not sure of is OOZIE-2306 (Oozie Health Check). It's a new feature and it might make sense to let it "bake" a while first? I'm also not sure it's quite ready yet. I'd also like to add a few others to the list: - OOZIE-2273 (MiniOozie does not work

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, Below is the list of issues, picked from currently available patches. I could not decide up any 'open' issue, If there is anything, please reply here. We can 'drop/add' more if required based on the feedback. Important is, how many of these we will be able to review and commit. I will

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, I looked into the commits (approx. 160), all looked good to me and should be included into the release. If there are things, which needs to be excluded, provide your comments. We still need to decide on the patch which are in progress status. On the upgrade side: Java version

Re: [SCOPE] Oozie 4.3.0 Release

We've been using a version of Hive/HCat based on 1.1.0 for over a year now with no problems. We did have to comment out a few lines in MiniHCatServer and MiniHS2 that were no longer needed: diff --git a/core/src/test/java/org/apache/oozie/test/MiniHCatServer.java

Re: [SCOPE] Oozie 4.3.0 Release

Let us explore changing the default hive version also to 1.x. 0.13 is old Thanks Venkat On 7/15/16, 11:31 AM, "Robert Kanter" wrote: I don't think we have any guidelines defined anywhere about when it's okay to change the minimum Java version, but perhaps we

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

Re: [SCOPE] Oozie 4.3.0 Release

Hi All, Any suggestions or comments on the scope for the release? Thanks, Abhishek > On Jul 13, 2016, at 3:07 AM, Abhishek Bafna wrote: > > Hi All, > > Oozie is starting the release process for Oozie 4.3.0. This thread is for > discussion about the scope of the

[SCOPE] Oozie 4.3.0 Release

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