https://bugzilla.wikimedia.org/show_bug.cgi?id=17322
--- Comment #11 from Tim Landscheidt <[email protected]> 2012-04-13 13:01:48 UTC --- (In reply to comment #10) > [...] > Generally, I'm kind of leery about auto-closing an auto-opening bugs. I may > commit half a fix for a bug and not want BZ to be closed yet. > [...] I have neither looked at the code I referenced nor worked in a project with auto-close, but I assume it would usually work in the way that the commit message would have to include some (semi-natural) phrase that triggers the close ("^This fixes bug #(\d+)\.", "^Fixes: (\d+)$", etc.) So if a commit doesn't fix a bug, you just don't use the exact phrase but maybe "This partially fixes bug #123"." and everything's as you expected. Regarding deployment, while I see your point, I think not using this facility would still leave the ambiguity: Has the deployment *really* been done? In the past, there have been delays when difficulties were encountered or manpower was short. Another automated comment on a closed bug will cause no harm, but *actively* inform the reporter who cares about the bug and not require *them* to do something. This of course *could* depend on how the deployment branch is organized, i. e. how a commit that is "reverted" is recognizable to some script so I would consider this part low priority. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
