For backward compatibility, we need to resolve
https://issues.apache.org/jira/browse/OOZIE-1789 for this release since this is
about sharelib installation.
On Friday, May 16, 2014 3:58 PM, Alejandro Abdelnur wrote:
the fact that other projects stay un the minor version to 'allow' incompat
the fact that other projects stay un the minor version to 'allow' incompat
changes whenever they want, well it is a matter of those projects and their
communities.
i'm proud that oozie has a great track of record in that front, including among
(yes among, not only between) major versions. and
>From 4.0 to 4.1, we should not have any DB upgrade and DB version should stay
>at 2.0, shouldn't it?
On Wednesday, May 14, 2014 4:48 PM, Robert Kanter wrote:
During the 3.x releases, we had an optional database change for MySQL to
change TEXT to MEDIUMTEXT; I don't think there was a required
During the 3.x releases, we had an optional database change for MySQL to
change TEXT to MEDIUMTEXT; I don't think there was a required one, but I
don't remember.
In any case, that's a good point about the other projects and how they
handle these things. So I'd agree then that we can have a databa
Not sure. I remember someone mentioning that schema upgrade should have
major version incremented in case of Oozie. But there was one release (3.1
->3.2 or something before I started working on Oozie) which had schema
change just incrementing minor version. If there was an already agreed
procedure
It might be tough work as the CLOB->BLOB conversion change touches a lot of
classes.
On Sun, May 11, 2014 at 9:25 PM, Robert Kanter wrote:
> Hi everyone,
>
> Should we start thinking about a 4.1.0 release? It's been a while since
> 4.0.0 (4.0.1 was to fix some critical things like not being ab
I agree; we'd also have to likely make two versions of each patch going
forward for 4.x and 5.x/trunk otherwise.
But are we "allowed" to make Oozie 4.0.x --> 4.1.0 require a database
upgrade?
On Tue, May 13, 2014 at 2:30 PM, Rohini Palaniswamy wrote:
> It might be tough work as the CLOB->BLOB c
I can drive the release.
Bowen
On Sunday, May 11, 2014 9:32 PM, Robert Kanter wrote:
Hi everyone,
Should we start thinking about a 4.1.0 release? It's been a while since
4.0.0 (4.0.1 was to fix some critical things like not being able to
compile) and I think we have about 200 additional JIRAs
Hi everyone,
Should we start thinking about a 4.1.0 release? It's been a while since
4.0.0 (4.0.1 was to fix some critical things like not being able to
compile) and I think we have about 200 additional JIRAs in master.
Are there any specific features that we'd want to put in 4.1.0 and wait
for?
