[
https://issues.apache.org/jira/browse/YETUS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377230#comment-15377230
]
Allen Wittenauer commented on YETUS-428:
----------------------------------------
I think the idea is great, but I'm not a fan of using -L here since we may want
to use labels for other identifier in the future (e.g., "only process JIRAs
with this label", which I could easily see happening.). Then we have an
ambiguity problem. Maybe use... I dunno, -X?
I kind of wish we would have never used single char options honestly. haha.
> 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, YETUS-428.01.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)
