bugzilla: allow change comment to mark bugs fixed Add a second regular expression used when scanning change comments. Bugs matched by this new regular expression have the bug comments and optionally hours updated as with the first regular expression, but they are also marked as fixed. The bug status and resolution to set to mark a bug as fixed can be configured. By default status is set to RESOLVED and resolution to FIXED, the default Bugzilla settings. For example, a change comment containing 'Fixes 1234 h1.5' will be added to bug 1234, the bug will have its working time increased by 1.65 hours, and the bug will be marked RESOLVED/FIXED. Change comments may contain both bug update and fix instructions. If the same bug ID occurs in both, the last instruction found takes precedence. The patch adds new bug states 'bug_status' and 'resolution' and actions to update them to the XMLRPC and XMLRPC/email access methods. XMLRPC does not support marking bugs as fixed when used with Bugzilla versions prior to 4.0. When used with an earlier Bugzilla version, a warning is issued and only comment and hours updated.

     1

# An example WSGI for use with mod_wsgi, edit as necessary

     2

# See http://mercurial.selenic.com/wiki/modwsgi for more information

     3

     4

# Path to repo or hgweb config to serve (see 'hg help hgweb')

     5

config = "/path/to/repo/or/config"

     6

     7

# Uncomment and adjust if Mercurial is not installed system-wide

     8

# (consult "installed modules" path from 'hg debuginstall'):

     9

#import sys; sys.path.insert(0, "/path/to/python/lib")

    10

    11

# Uncomment to send python tracebacks to the browser if an error occurs:

    12

#import cgitb; cgitb.enable()

    13

    14

# enable demandloading to reduce startup time

    15

from mercurial import demandimport; demandimport.enable()

    16

    17

from mercurial.hgweb import hgweb

    18

application = hgweb(config)