www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herbert Duerr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5004) Automatic updates from Repository into Bugzilla
Date Thu, 22 Nov 2012 08:55:00 GMT

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

Herbert Duerr commented on INFRA-5004:

Thanks to Daniel for pointing out that the svnpubsub service is now available at http://svn-master.apache.org:2069/commits/xml
> Automatic updates from Repository into Bugzilla
> -----------------------------------------------
>                 Key: INFRA-5004
>                 URL: https://issues.apache.org/jira/browse/INFRA-5004
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: Bugzilla, Subversion
>            Reporter: Herbert Duerr
>            Priority: Minor
> Having change management automation where code commits trigger updates of their corresponding
bugzilla entries would be very helpful.
> There seem to be several open-source tools available for this, one of the most prominent
ones for SVN-Bugzilla integration seems to be SCMBUG (http://www.mkgnu.net/scmbug).
> In the case of Apache OpenOffice there is the convention to mention e.g. "#i123456#"
in the commit message summary to indicate that a particular change was done for solving issue
number 123456. If the revision number of the commit was used to add a comment to that issue
with e.g. "Revision 11223344 committed" and eventually the commit message summary then this
would be extremely helpful.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message