www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-3493) JIRA reference pre-commit hook for Apache Qpid
Date Sun, 13 Mar 2011 01:58:59 GMT

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

Gavin commented on INFRA-3493:
------------------------------

fwiw this is what we were taught at Apache Forrest and self governance worked well. When I
forgot, I was reminded and told to correct the log. Like other workflows that everyone gets
used to, this is just another. Escalating a reinforcement and Infra level is overkill imho

> JIRA reference pre-commit hook for Apache Qpid
> ----------------------------------------------
>
>                 Key: INFRA-3493
>                 URL: https://issues.apache.org/jira/browse/INFRA-3493
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Robbie Gemmell
>            Priority: Minor
>
> The Apache Qpid project would like to have a Subversion pre-commit hook added to enforce
that commit log messages for the project contain either a JIRA issue reference (eg QPID-1234)
or alternatively include NO-JIRA to escape enforcement of the commit hook. If neither is found,
the commit would fail and alert the committer to either include an issue reference or use
NO-JIRA to escape the script.
> 1) Can we have such a commit hook?
> 2) If so, would you implement it or would we need to provide an appropriate script?
> Thanks,
> Robbie

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message