I have written two extensions, available here: http://hg.mozilla.org/users/bsmedberg_mozilla.com/hgpoller/ revision d0a8c7314fff These extensions work with mercurial 1.0 to provide extra information from the hgweb interface. The README file in my repository has information about how to install them. The feed provided by pushlog-feed will help fix bug 421175 and make the data collected in bug 422758 public.
I do not think we need to block mozilla-central on this bug. We're collecting the data, and will report it in due course.
Will we have any better way to answer the question "Who broke the tree?"?
Assuming that people don't lie about the username in commit messages, I think we can figure out the relevant data from hg log, in the meantime.
upgraded to mercurial 1.0 and added the two extensions to the mozilla-central repo.
Aravind, the extensions don't appear to be working: To test pushlog-feed, visit a URL of this form: http://hg.mozilla.org/mozilla-central/index.cgi/?pushlog The results should be an Atom feed. For an example of correct functioning, see http://office.smedbergs.us/hgwebdir.cgi/mozilla-central/pushlog To test hgwebjson, visit a URL of this form: http://hg.mozilla.org/mozilla-central/index.cgi/?jsonheads The results should be a JSON text file. For an example of correct functioning, see http://benjamin.smedbergs.us/hgwebdir.cgi/mozilla-central/jsonheads
With the config-file fix this is now working on mozilla-central. Can we either 1) enable these globally 2) turn these on for the other toplevel repos: * actionmonkey * actionmonkey-tamarin * tamarin-central * tamarin-tracing
So, the url you had was wrong. It should be http://hg.mozilla.org/mozilla-central/index.cgi/jsonheads http://hg.mozilla.org/mozilla-central/index.cgi/pushlog I enabled logging and those extensions globally (for all repos).
Hey Aravind, did these get turned on for user repos, too? I get an error on this URL: http://hg.mozilla.org/users/bhearsum_mozilla.com/my-moz-central/index.cgi/pushlog
The extensions are available, but we're not recording push information for user repos. This is by design: user repos may have multiple heads, and the push logging feature doesn't know how to record anything but a single head.