Doug, You are right, there should not be any changes in the stats. Bugs are mapped to release only by date, target milestone is not taken into account. For resolved bugs metric Stackalytics uses 'date_fix_commited' field, for filed bugs metric - 'date_created'.
Thanks, Ilya 2015-11-10 0:53 GMT+03:00 Doug Hellmann <d...@doughellmann.com>: > Stackalytics experts, > > When we roll out the launchpad process changes described in my earlier > email [1], we will no longer be targeting bugs as part of closing them. > > Thierry raised a concern that this might break the way stackalytics > calculates closed bug statistics for a cycle. Looking at the code > in [2] and [3], I see it querying by date range and looking at the > status, but not looking at the milestone to which the bug is targeted. > > Am I right in believing that we won't have any change in our > statistics gathering if we go ahead with the current plan? > > Thanks, > Doug > > [1] > http://lists.openstack.org/pipermail/openstack-dev/2015-November/078301.html > [2] > http://git.openstack.org/cgit/openstack/stackalytics/tree/stackalytics/processor/main.py#n99 > [3] > http://git.openstack.org/cgit/openstack/stackalytics/tree/stackalytics/processor/record_processor.py#n511 >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
