[
https://issues.apache.org/jira/browse/YETUS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177292#comment-15177292
]
Andrew Wang commented on YETUS-321:
-----------------------------------
bq. 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.
I'd like to get to a paradigm where lint is treated like a compile error, so
broken release docs never get released. This initial step of being able to
selectively disable filters is a partial solution; if we had per-JIRA "ignore"
options, I think that's complete. We can also turn on lint printing by default
so it always shows up for RMs, and if the "--lint" flag is specified, also set
a non-zero status code and wipe the directories on error.
Happy to do the above work if this sounds good.
> 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)
