[jira] [Commented] (OOZIE-155) GH-137: release-log.txt file misses 2.2.1 & 2.2.2 features/fixes

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099842#comment-13099842 ] 

Hadoop QA commented on OOZIE-155:
---------------------------------

rvs remarked:
Strictly speaking it doesn't:

http://github.com/yahoo/oozie/blob/2.2/release-log.txt

The trouble is that the commit which introduced those things sits 
on top of actual 2.2.1 and 2.2.2 release points:

http://github.com/yahoo/oozie/commit/e76b0e5babf71926f12c37ab0df65dfd2626b60e

That said, at this point it would be pretty much impossible to splice things
in, since we depend on the 2.2 branch the way it is.

Moving forward, I'll be using a modified maven release plugin to take care
of release-log.txt

Anyway, I'm tempted to close this, as an unfortunate WILL NOT FIX,
but if you have good ideas on how to fix it -- I'm all ears.

Please let me know.

> GH-137: release-log.txt file misses 2.2.1 & 2.2.2 features/fixes
> ----------------------------------------------------------------
>
>                 Key: OOZIE-155
>                 URL: https://issues.apache.org/jira/browse/OOZIE-155
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira