[
https://issues.apache.org/jira/browse/YETUS-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549877#comment-16549877
]
Allen Wittenauer commented on YETUS-566:
----------------------------------------
What if release doc maker was given a flag to automatically close JIRAs that
were in 'resolved' state?
> Release candidate contribution guide missing jira work to verify fix version.
> -----------------------------------------------------------------------------
>
> Key: YETUS-566
> URL: https://issues.apache.org/jira/browse/YETUS-566
> Project: Yetus
> Issue Type: Bug
> Components: website and documentation
> Affects Versions: 0.6.0
> Reporter: Sean Busbey
> Priority: Major
>
> the [contribution guide on
> releases|http://yetus.apache.org/contribute/releases/] has a section on "work
> in JIRA", but that section never mentions
> * checking that issues targeting the RC are closed
> * verifying that the closed issues with the fix version are present in the
> artifact
> We treat JIRA as the source of truth, so the second one isn't that big of a
> deal. But giving folks guidance on some ways to gut check things would still
> be beneficial.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
