You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Herbert Duerr (JIRA)" <ji...@apache.org> on 2012/09/05 11:50:07 UTC

[jira] [Updated] (INFRA-5004) Automatic updates from Repository into Bugzilla

     [ https://issues.apache.org/jira/browse/INFRA-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herbert Duerr updated INFRA-5004:
---------------------------------

    Status: Waiting for Infra  (was: Waiting for user)
    
> 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