Hi Andras,

Thanks for bringing this up!

Yes, it would be great to have Oozie 5 released.
I'll go though the Jira to see if there are other outstanding issues I
consider as blockers and set their target versions accordingly.

gp



On Tue, Mar 13, 2018 at 12:53 PM, Andras Piros <and...@apache.org> wrote:

> Hi everyone,
>
> it's been more than a month now that *Oozie 5.0.0-beta1 has been released
> <http://mail-archives.apache.org/mod_mbox/oozie-user/
> 201801.mbox/raw/%3CCA%2Bng5ZQD0XOo2EehTGL9NT9ZWLCTvJ
> uQAvYuCyfCdCbybyg91Q%40mail.gmail.com%3E/1>*.
> Since then, lots of improvements and fixes, as well as *an important
> security fix
> <http://mail-archives.apache.org/mod_mbox/oozie-user/201802.mbox/raw/%
> 3CCABBupGWtC2vN-JzXWeuDaN-_bP6yzRJhK%2BDAfr%3DgSGLZJGbFCQ%40mail.gmail.
> com%3E/1>*
> have been committed to master.
>
> It's time to move towards 5.0.0 GA. I'm volunteering to act as a release
> manager.
>
> I've identified so far *following 5.0.0 JIRAs
> <https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%2012311620%20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20%3D%205.0.0%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC>*
> still unresolved of interest, including:
>
>    - *OYA: Update documentation
>    <https://issues.apache.org/jira/browse/OOZIE-2600>*
>    - *OYA: Update example workflows to newest schemas
>    <https://issues.apache.org/jira/browse/OOZIE-2814>*
>    - *[Umbrella] Fix flaky tests in Oozie
>    <https://issues.apache.org/jira/browse/OOZIE-3111>*
>
> Some non-blocker ones of the unresolved JIRAs originally targeted for 5.0.0
> I've pushed out *to 5.1.0
> <https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%2012311620%20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20%3D%205.1.0%20AND%20updated%20%3E%20%
> 272018%2F03%2F12%27%20ORDER%20BY%20%20priority%20DESC%2C%20key%20ASC>*,
> other less important ones *to trunk
> <https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%2012311620%20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20%3D%20trunk%20AND%20updated%20%3E%20%
> 272018%2F03%2F12%27%20ORDER%20BY%20%20priority%20DESC%2C%20key%20ASC>*.
> Please feel free to step up if you think an important issue has to be
> targeted for 5.0.0.
>
> Once those are fixed we can roll on with the release process.
>
> Regards,
>
> Andras
>



-- 
Peter Cseh
Software Engineer
<http://www.cloudera.com>

Reply via email to