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 <https://cwiki.apache.org/confluence/display/Hive/HowToContribute#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 <http://www.cloudera.com>
