[
https://issues.apache.org/jira/browse/YETUS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Yadava updated YETUS-428:
------------------------------
Attachment: YETUS-428.00.patch
h5. Changes in the .00 patch
- Made changes to fallback to reading labels in case "Hadoop Flags" field is
missing in the issue.
- Default label is 'backward-incompatible' but provided an option to override
this value
- Updated documentation.
> Provide fallback option to mark issues as incompatible
> ------------------------------------------------------
>
> Key: YETUS-428
> URL: https://issues.apache.org/jira/browse/YETUS-428
> Project: Yetus
> Issue Type: New Feature
> Components: Release Doc Maker
> Reporter: Ajay Yadava
> Assignee: Ajay Yadava
> Attachments: YETUS-428.00.patch
>
>
> Currently the releasedocmaker script marks an issue as "Incompatible" on the
> basis of "Hadoop Flags" field. However, many projects (e.g. Apache Falcon)
> don't use this field and follow the convention of adding a label
> 'backward-incompatible' to mark the issue as an "Incompatible" change.
> It will be nice if we could use Labels as the fallback option in case "Hadoop
> Flags" field is blank.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
