Thu, 01 Mar 2012 14:50:31 +0000 bugzilla: add xmlrpcemail submission for Bugzilla 3.6 email interface
Jim Hague <jim.hague@acm.org> [Thu, 01 Mar 2012 14:50:31 +0000] rev 16224
bugzilla: add xmlrpcemail submission for Bugzilla 3.6 email interface Some of the formatting details required for bug submission via email changed between Bugzilla 3.4 and 3.6. Bugzilla 3.4 requires lines of the form '@fieldname = value', while 3.6 wants '@fieldname value'. Also the field @bug_id in 3.4 becomes @id in 3.6. Bugzilla up to and including 4.0 also recognises the 3.4 format. To save surprises in the future, check the Bugzilla version and use the 3.6 format from all major versions >= 4. At some point we will drop support for Bugzilla prior to 3.6 and support the new format only.
Thu, 01 Mar 2012 15:27:24 +0000 bugzilla: allow change comment to mark bugs fixed
Jim Hague <jim.hague@acm.org> [Thu, 01 Mar 2012 15:27:24 +0000] rev 16223
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.
Thu, 01 Mar 2012 15:25:37 +0000 bugzilla: extract optional hours from commit message and update bug time
Jim Hague <jim.hague@acm.org> [Thu, 01 Mar 2012 15:25:37 +0000] rev 16222
bugzilla: extract optional hours from commit message and update bug time If an 'hours' group is present in the bug matching regular expression, and that group contains a float value, update the bug working time in Bugzilla with those hours. The patch adds a key 'hours' to the bug state dictionary, and adds support for the key to the XMLRPC and XMLRPC/email access methods. The MySQL access method is not supported; a warning is given.
Thu, 01 Mar 2012 14:51:40 +0000 bugzilla: modify access interface to include new bug states
Jim Hague <jim.hague@acm.org> [Thu, 01 Mar 2012 14:51:40 +0000] rev 16221
bugzilla: modify access interface to include new bug states As a first step to allowing comment text to update bug state, rework the Bugzilla access interface to use a dictionary keyed on bug ID. Dictionary entries will contain new state info in future changes.
Sat, 03 Mar 2012 23:14:31 -0600 wix: add phases help text and two more translations (issue 3288) stable
Steve Borho <steve@borho.org> [Sat, 03 Mar 2012 23:14:31 -0600] rev 16220
wix: add phases help text and two more translations (issue 3288)
Fri, 02 Mar 2012 11:46:18 -0300 debugbuilddag: fix starting a dag on a non-default branch stable
Wagner Bruna <wbruna@softwareexpress.com.br> [Fri, 02 Mar 2012 11:46:18 -0300] rev 16219
debugbuilddag: fix starting a dag on a non-default branch
Fri, 24 Feb 2012 11:02:21 +0100 debugrevspec: pretty print output
Patrick Mezard <patrick@mezard.eu> [Fri, 24 Feb 2012 11:02:21 +0100] rev 16218
debugrevspec: pretty print output Before: ('func', ('symbol', 'reverse'), ('func', ('symbol', 'sort'), ('list', ('or', ('symbol', '2'), ('symbol', '3')), ('symbol', 'date')))) After: (func ('symbol', 'reverse') (func ('symbol', 'sort') (list (or ('symbol', '2') ('symbol', '3')) ('symbol', 'date')))) v2: - Rebased on stable to avoid having to merge tests output
Fri, 02 Mar 2012 21:43:55 +0200 readme: mention how to run in-place
Ross Lagerwall <rosslagerwall@gmail.com> [Fri, 02 Mar 2012 21:43:55 +0200] rev 16217
readme: mention how to run in-place The README describes how to install Mercurial but it does not describe how to run it in place (for developers). This adds a short paragraph to the README describing how to do run Mercurial inplace.
Fri, 02 Mar 2012 14:12:06 -0600 merge with stable
Matt Mackall <mpm@selenic.com> [Fri, 02 Mar 2012 14:12:06 -0600] rev 16216
merge with stable
Fri, 02 Mar 2012 14:11:06 -0600 merge with i18n stable
Matt Mackall <mpm@selenic.com> [Fri, 02 Mar 2012 14:11:06 -0600] rev 16215
merge with i18n
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip