Filter out robot commits in stats

Bug #723726 reported by Jonathan Lange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr-stats
Triaged
Medium
Unassigned

Bug Description

The "bzr stats" output for lp:launchpad starts off like this:

$ bzr stats
getting ancestry
getting revisions
10046 Launchpad Patch Queue Manager <email address hidden>
5825 Canonical.com Patch Queue Manager <email address hidden>
     Other email addresses:
     3061 <email address hidden>
     2764 <email address hidden>
4990 Jonathan Lange <email address hidden>
     Other names:

The first two "committers" aren't actually interesting at all. They are merely robots that land things on behalf of humans.

This sort of ties in to bug 723723. What I actually want are stats about humans for mainline commits.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

We could add a --ignore flag to allow you to specify committers to ignore.

An alternative would be to have pqm, tarmac, etc set a revision property (if you have a hammer, everything looks like a nail...) and have bzr-stats pick up on that. Again, this wouldn't really help with historic commits.

Changed in bzr-stats:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 723726] Re: Filter out robot commits in stats

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/23/2011 8:45 AM, Jelmer Vernooij wrote:
> We could add a --ignore flag to allow you to specify committers to
> ignore.
>
> An alternative would be to have pqm, tarmac, etc set a revision property
> (if you have a hammer, everything looks like a nail...) and have bzr-
> stats pick up on that. Again, this wouldn't really help with historic
> commits.
>
> ** Changed in: bzr-stats
> Status: New => Triaged
>
> ** Changed in: bzr-stats
> Importance: Undecided => Medium
>

What he wants, though, is to say that commit 10254 in the Launchpad
mainline was committed by PQM, but the work inside that branch was done
by Jonathan Lange, so he gets 1 point for a mainline commit of work he
committed.

At least, that is what I get out of what he said.

So iterate the mainline revisions, find what revisions were merged for
each mainline, each author listed gets 1 commit point for it landing in
mainline. (this could include the person landing it, or not)

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1lPZwACgkQJdeBCYSNAAOi4wCeM8wU0Ld+Fz6LUEp3bRb1RPKW
6loAnivWl/txkWxD3AHF1TPezzXfKPX/
=jIvj
-----END PGP SIGNATURE-----

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.