| Summary: | add a bugzilla / mercurial extension | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Sylvain <sylvain.becker> |
| Component: | website | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED WONTFIX | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | CC: | philipp.wiesemann |
| Version: | HG 2.1 | ||
| Hardware: | x86_64 | ||
| OS: | Windows 7 | ||
|
Description
Sylvain
2014-09-17 13:57:12 UTC
I have worked in a few compagnies, and this is mecanism is absolutly great to use ... For instance, when you commit in mercurial, you put the commit message "fix function blabla blabla. Ref #1234". If ticket of Bugzilla #1234 is not opened, it will reject the commit since bug is closed. Otherwise, the commit is pushed, and the "commit" message is automatically added as a message to the Bugzilla ticket #1234, with a html link to the commit diff revision (eg https://hg.libsdl.org/SDL/rev/bf0989bde198). And, symmetrically, when you browse the commits from https://hg.libsdl.org/SDL, if you click "Ref #1234", it is a html link to the Bugzilla ticket. When people follows Bugzilla tickets they can see the commits related. And vice versa, when they see the commit, they can jump quickly to see what issue it addresses ... Usually companies make this "hook" mandatory but that's can be just optionnal also. In fact you and others already do it manually (eg https://bugzilla.libsdl.org/show_bug.cgi?id=3451), but that could be done automatically (with the reverse link!) ! Cheers, Sylvain The updated URL is: https://www.mercurial-scm.org/wiki/BugzillaExtension I'd prefer to keep the current method, where the important parts of the bug report are included directly in the Mercurial commit. This will keep the history relevant if we switch bug reporting systems in the future. Thanks though! |