[
https://issues.apache.org/jira/browse/HADOOP-11807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513323#comment-14513323
]
Allen Wittenauer commented on HADOOP-11807:
-------------------------------------------
With the exception of maybe the version string checks(*), no extra JQL should
be required. releasedocmaker already does the JQL and fills in the fields of
python data structure. lint mode is really just going through that precomputed
data structure and reporting problems.
We don't want it part of the maven build; this mode needs to be part of the
create-release script instead, because that's when it matters. So errors
should not be markdown format, but instead printed to the screen like the
current release note warning message. lint mode should exit with failure on
errors so that it can fail the create-release script.
* - version string checks are things like having two numeric versions assigned.
This isn't a fatal error, but definitely needs for the release manager to
investigate. Anyway, IIRC, the query does get all the versions assigned for
that issue, even beyond the one requested.
> add a lint mode to releasedocmaker
> ----------------------------------
>
> Key: HADOOP-11807
> URL: https://issues.apache.org/jira/browse/HADOOP-11807
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, documentation
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Priority: Minor
>
> * check for missing components (error)
> * check for missing assignee (error)
> * check for common version problems (warning)
> * add an error message for missing release notes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
