Hi,
I think we should be good to release 4.0 early next week. Mona will be
rolling out the release.
Pending:
- https://issues.apache.org/jira/browse/OOZIE-1482 - backward
compatibility with older servers for frequency in json response. Patch is
already up.
- A minor issue with db upgrade
https://issues.apache.org/jira/browse/OOZIE-1465 has a small patch to make
some constants public. These are very useful for EL extensions. Can you
please merge to 4.0 branch
-Shwetha
On Sat, Jul 20, 2013 at 5:36 AM, Rohini Palaniswamy rohini.adi...@gmail.com
wrote:
This is done now. Changed
Hi Rohini,
What's the status of branch 4? Do you think you'll be sending out a vote
for the release soon?
thanks
- Robert
On Wed, Jul 24, 2013 at 2:27 AM, Shwetha GS shwetha...@inmobi.com wrote:
https://issues.apache.org/jira/browse/OOZIE-1465 has a small patch to make
some constants
We discovered a couple of critical bugs around Bundle Kill command. We
will be patching branch 3.3, branch-4.0 and trunk in the next few days and
then would be comfortable preparing for the release.
--
Mona
On 7/24/13 11:36 AM, Robert Kanter rkan...@cloudera.com wrote:
Hi Rohini,
What's the
Do you mean the Fix Version field?
Yes.
I know that many JIRAs are using that
to also mean the target version, which is a field we don't have
Fix Version is the equivalent of bugzilla Target Version.
I'm sure there are some JIRAs marked with
Fix Version as trunk that we don't want in
Planning to do a bulk update of the Fixed version of jiras to branch-4.0
tomorrow. Currently they are marked as trunk. Please let know if there are
any objections.
Regards,
Rohini
On Fri, Jun 28, 2013 at 10:27 PM, Rohini Palaniswamy
rohini.adi...@gmail.com wrote:
Created
Do you mean the Fix Version field? I know that many JIRAs are using that
to also mean the target version, which is a field we don't have (perhaps
we should have that field?). I'm sure there are some JIRAs marked with
Fix Version as trunk that we don't want in 4.0, right?
- Robert
On Fri, Jul
Hi,
I am planning to branch trunk as branch-4.0 and trash the current
branch-4.0 today evening. Discussed this with some of the folks during the
summit. This will facilitate releasing HCat integration, JMS notifications
for job and SLA and SLA monitoring as Oozie 4.0 which we are done with
That change is reverted by OOZIE-1436. Can you review
https://reviews.apache.org/r/12164/ and confirm?
We can keep OOZIE-1437 open to deal the problems we will face when having
a 'proper' fix for the clob/varchar issues.
Thanks,
Virag
On 6/28/13 11:12 AM, Robert Kanter rkan...@cloudera.com
Ah, you're right; thanks.
I reviewed the patch, but I'd like someone else to also take a look because
I'm not a DB expert.
- Robert
On Fri, Jun 28, 2013 at 11:30 AM, Virag Kothari vi...@yahoo-inc.com wrote:
That change is reverted by OOZIE-1436. Can you review
Created http://svn.apache.org/viewvc/oozie/branches/branch-4.0/.
Patches yet to be done for branch-4.0.
OOZIE-1379 Generate SLA end_miss event only after confirming against
persistent store
OOZIE-1249 and OOZIE-1430 Documentation for JMS notifications and SLA
monitoring
OOZIE-1405 Fix flakey
11 matches
Mail list logo
