[
https://issues.apache.org/jira/browse/YETUS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177228#comment-15177228
]
Andrew Wang commented on YETUS-321:
-----------------------------------
I'm wrapping my head around releasedocmaker, I would like to pursue a bigger
refactor of main() as part of this. At a high-level:
* Break out a {{Linter}} class that contains all lint functionality and checks.
As a result, generated release docs would no longer include lint-related
warnings. IMO there's no point nagging about missing fields in the release
notes themselves, at that point the ship has sailed. Having it tied together
also makes it hard to modularize the code.
* Split option parsing and validation to a new function, to shrink main()
* lint filters will be specified via a new {{--lint-opts}} flag, since that's
the only compatible-ish way of doing the filter parsing. optparse cannot handle
optional values.
Not sure what compatibility policy Yetus has right now, but the above would be
fine for Hadoop.
> 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)
