[jira] [Commented] (YETUS-428) Provide fallback option to mark issues as incompatible

["Ajay Yadava (JIRA)" <ji...@apache.org>]

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

Ajay Yadava commented on YETUS-428:
-----------------------------------

I am thinking to provide an option to specify the label to be used for indicating the backward-incompatibility with default value being 'backward-incompatible'. Thoughts?

> 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
>
> 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)