incorrect categorization of integrated projects for icehouse

Bug #1308347 reported by dan wendlandt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stackalytics
Fix Released
High
Ilya Shakhat

Bug Description

I noticed that stackalytics was recently broken when looking at the following filter:

http://www.stackalytics.com/?release=icehouse&metric=commits&project_type=integrated&module=&company=&user_id=

This should show contributions for integrated projects in icehouse, but it incorrect counts sahara as an integrated project for icehouse, when in fact it was approved as an integrated project for the juno release.

This is an especially bad bug in my opinion as it could be (incorrectly, I assume) interpreted as Mirantis "cooking the books" to try and make its contributions for integrated projects in Icehouse seem higher (given that they have a 250+ contribution in Sahara in icehouse nearly doubles the number of Mirantis integrated commits).

Given that the default "OpenStack" query includes tons of peripheral projects, to me the "integrated" query is the most useful for showing involvement in core OpenStack. I tend to point people to stackalytics.com as a source for stats like this, and when they are wrong, it undermines the value of the site.

Or perhaps I'm misunderstanding something here?

Revision history for this message
Ilya Shakhat (shakhat) wrote :

The fix requires correct historical data in official programs.yaml - the thing that is discussed in https://review.openstack.org/#/c/81859/
The current plan is to implement needed functionality and temporary use a copy of programs.yaml

Changed in stackalytics:
importance: Undecided → High
assignee: nobody → Ilya Shakhat (shakhat)
status: New → Triaged
Revision history for this message
dan wendlandt (danwent) wrote :

Thanks Ilya, that makes sense.

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to stackalytics (master)

Fix proposed to branch: master
Review: https://review.openstack.org/89338

Changed in stackalytics:
status: Triaged → In Progress
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to stackalytics (master)

Reviewed: https://review.openstack.org/89338
Committed: https://git.openstack.org/cgit/stackforge/stackalytics/commit/?id=34013400e7d7e57656beae1181ba4e7f5ad657ad
Submitter: Jenkins
Branch: master

commit 34013400e7d7e57656beae1181ba4e7f5ad657ad
Author: Ilya Shakhat <email address hidden>
Date: Mon Apr 21 16:01:56 2014 +0400

    Support retrospective mapping of project type to modules

    During its development the module may move from one project type to others
    (e.g. in some release it may become incubated or integrated). This patch
    adds support of new version of official programs.yaml file
    (https://raw.github.com/openstack/governance/master/reference/programs.yaml)
    that supports specifying the first version when the module gets promoted up
    to the next status.

    Closes bug 1308347

    Change-Id: I9d83910f209afd81cab94aecac36f4cb08111c35

Changed in stackalytics:
status: In Progress → Fix Committed
Revision history for this message
Ilya Shakhat (shakhat) wrote :

Deployed in production with the trunk version of governance's programs.yaml:
 http://stackalytics.com/?release=juno&project_type=integrated - integrated in Juno (11 projects)
 http://stackalytics.com/?release=icehouse&project_type=integrated - integrated in Icehouse (10 projects)
 http://stackalytics.com/?release=diablo&project_type=integrated - just 3 projects in Diablo

Ilya Shakhat (shakhat)
Changed in stackalytics:
milestone: none → 0.5
status: Fix Committed → Fix Released
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.