[ 
https://issues.apache.org/jira/browse/YETUS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172791#comment-15172791
 ] 

Sean Busbey commented on YETUS-226:
-----------------------------------

bq. The check for "@author" probably triggered just because of sample 
test-patch output in the doc, so it's not relevant.

Yep, exactly. Unfortunately we have no way to differentiate for the case.

bq. Are the ruby-lint warnings relevant?

I don't think so, no. It's evaluating config.rb as a normal Ruby file and thus 
rightly complaining that we use symbols from Middleman without requiring 
middleman. But config.rb isn't a normal Ruby file; it's Middleman specific and 
I don't believe it's correct to have middleman related requires statements. 
From when I last looked, there didn't seem to be a straight-forward way to tell 
ruby-lint these cases were fine but e.g. lacking requires for other modules was 
not.

> Document release process
> ------------------------
>
>                 Key: YETUS-226
>                 URL: https://issues.apache.org/jira/browse/YETUS-226
>             Project: Yetus
>          Issue Type: Improvement
>          Components: website and documentation
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 0.2.0
>
>         Attachments: YETUS-226.1.patch, YETUS-226.2.patch, YETUS-226.3.patch, 
> YETUS-226.4.patch, YETUS-226.5.patch, YETUS-226.6.patch, YETUS-226.7.patch
>
>
> document how to handle making a release candidate and call a vote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to