Re: Oozie 4.x maintenace branch

[Robert Kanter]

Hadoop does something like this with the branch-2 (Hadoop 2.x) and trunk
(Hadoop 3.x) branches.  They even have their test-patch Jenkins thing setup
such that you can run patches against different branches.

This seems like a good idea.  Though I think we should:

   1. Define a timeframe for how long Oozie 4 would be maintained.  For
   instance, we could say Oozie 4.x will be maintained until MM/DD/YY, where
   we will re-evaluate if it should continue to be maintained to another
   future date or dropped.
   2. Define some guidelines on the sorts of things that will go into the
   Oozie 4 branch.  As Oozie 5 starts to diverge more and more from Oozie 4,
   the cost of requiring contributors to post two (possibly very different)
   versions of their patches and committers to review both will become more
   and more expensive.  Perhaps something like bug fixes only, unless the
   effort is deemed too high (which is subjective, I know).


- Robert

On Mon, Feb 6, 2017 at 2:57 AM, Peter Cseh  wrote:

> Hi all,
>
> OOZIE-1770 is (hopefully) getting close to be committed.
> It will break backward compatibility and remove huge parts of core Oozie
> code.
> There are multiple Oozie deployments out there which will be on version 4.x
> for some time.
> I'm wondering if It's a good idea to create a branch-4 along master with
> backward compatibility with 4.x to have issues fixed for a future possible
> 4.4.0 or 4.3.1. for users who don't want their Oozie upgraded to 5.x.
>
> I'm thinking about something similar to Hive's
>  HowToContribute-UnderstandingHiveBranches>
> policy
> for branch-1 and master.
>
> I don't know what's the process for this, I guess this would be a PMC
> decision, I just wanted to start the discussion about this topic.
>
> Any thoughts?
> Cheers,
> gp
>
>
> --
> Peter Cseh
> Software Engineer
> 
>

Oozie 4.x maintenace branch

[Peter Cseh]

Hi all,

OOZIE-1770 is (hopefully) getting close to be committed.
It will break backward compatibility and remove huge parts of core Oozie
code.
There are multiple Oozie deployments out there which will be on version 4.x
for some time.
I'm wondering if It's a good idea to create a branch-4 along master with
backward compatibility with 4.x to have issues fixed for a future possible
4.4.0 or 4.3.1. for users who don't want their Oozie upgraded to 5.x.

I'm thinking about something similar to Hive's

policy
for branch-1 and master.

I don't know what's the process for this, I guess this would be a PMC
decision, I just wanted to start the discussion about this topic.

Any thoughts?
Cheers,
gp


-- 
Peter Cseh
Software Engineer