https://bugzilla.wikimedia.org/show_bug.cgi?id=17322

--- Comment #10 from Chad H. <[email protected]> 2012-04-12 22:15:05 UTC 
---
If we make use of the feature described in issue 124 (see comment 9), we could
easily use patchset-created to ping BZ with a "A change for this bug was pushed
for review in gerrit 123 [project: foo; branch; bar]" We could follow up with
"Gerrit change 123 was merged on DATE [project: foo; branch: bar]"

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. 

(In reply to comment #8)
> I don't know whether the configuration management of WMF wikis falls under SVN
> as well, but I'd also find it extremely helpful if a bug not only received a
> "Fixed in r4711." comment, but also that the fix went live on labs (or
> whereever) and finally on the main farm.
> 

The plan right now is to have deployment-labs running master (so it'll get all
the latest changes) and deploy master to the cluster every 2 weeks. So I think
in the long run this will be a little bit less of an issue. Once we get into
the cycle you'll be able to assume that anything over ~2 weeks old has been
deployed.

-- 
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

Reply via email to