[
https://issues.apache.org/jira/browse/YETUS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177245#comment-15177245
]
Allen Wittenauer commented on YETUS-321:
----------------------------------------
bq. IMO there's no point nagging about missing fields in the release notes
themselves, at that point the ship has sailed.
For end users, it's a huge flag that while there isn't a release note, they may
want to go look at the JIRA to see what is actually happening. It's also
extremely useful for REs as a reminder that they really should go fix that
before release when they do that visual inspection of the notes.
bq. Not sure what compatibility policy Yetus has right now, but the above would
be fine for Hadoop.
We are very much still in the "no compatibility rules" mode.
> Add flag to releasedocmaker.py to ignore missing component in lint mode
> -----------------------------------------------------------------------
>
> Key: YETUS-321
> URL: https://issues.apache.org/jira/browse/YETUS-321
> Project: Yetus
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Attachments: yetus-321.001.patch, yetus-321.002.patch
>
>
> Not all projects require the "component" field in JIRA. For these projects,
> it would be nice to ignore the "missing component" errors in lint mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
