We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2731 - add a bugzilla / mercurial extension
Summary: add a bugzilla / mercurial extension
Status: RESOLVED WONTFIX
Alias: None
Product: SDL
Classification: Unclassified
Component: website (show other bugs)
Version: HG 2.1
Hardware: x86_64 Windows 7
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-17 13:57 UTC by Sylvain
Modified: 2016-10-14 17:39 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvain 2014-09-17 13:57:12 UTC 
Hi,

This is not an SDL bug, but an improvement suggestion.
A BugzillaExtension could be added to Mercurial so that "changesets" and "tickets" are linked more closely together !

see:

http://mercurial.selenic.com/wiki/BugzillaExtension

Cheers,

Sylvain
Comment 1 Sam Lantinga 2016-10-14 17:36:57 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
Comment 2 Sam Lantinga 2016-10-14 17:38:23 UTC 
The updated URL is:
https://www.mercurial-scm.org/wiki/BugzillaExtension
Comment 3 Sam Lantinga 2016-10-14 17:39:18 UTC 
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!