POMs in master should be bumped to 2.2.1-SNAPSHOT

[tucu00]

No description provided.

[rvs]

Given that master is our road to 3.0.0 shouldn't it be 3.0.0-SNAPSHOT ?

[tucu00]

I don't know, never saw what is the roadmap/plan....

[rvs]

Well, the roadmaps is easy to see now:
http://github.com/yahoo/oozie/issues/labels/oozie-3.0

But you didn't answer my question ;-)

[tucu00]

I'm OK to bump up POMs to 3.x in master.

Still, not clear to me how we'll proceed with 2.x development.

[rvs]

Oozie 2.x is in a 100% maintenance mode as far as Y! team is concerned. The only changes going there would be the ones needed to provide relief for urgent production issues. Everything else should be going into master as part of our work on 3.0.

To you, the 2.2 branch should not be of any interest (unless Cloudera already has customers running 2.2 in production).

Of course, the reason I'm asking this question about master is whether we're ready to bite the bullet and sprint towards 3.0 or whether having an intermediate goal(s) of 2.X releases
would be more convenient.

That said, the only reason I could think of where 2.3 would make sense would be if we decide to take care of the technical debt first, before taking onto the 3.0 issues (which doesn't seem to be the case).