Remove has_many association from Reviewer and Participant
Get on_optimize to work
In rake run:analyze populate a new field on participant called sheriff_hours that totals the number of hours that that participant was on rotation prior to the creation of this code review. Aggregate all types of sheriffs into this count - no need to filter out different types of sheriffs
Also in rake run:analyze aggregate the above count into the code review so we know how many hours the code review had in total.
Add a release_filepath metric that averages the total number of code review hours per code review.
Make the association in rake run:results that tests this
has_many
association from Reviewer and Participanton_optimize
to workrake run:analyze
populate a new field on participant calledsheriff_hours
that totals the number of hours that that participant was on rotation prior to the creation of this code review. Aggregate all types of sheriffs into this count - no need to filter out different types of sheriffsrake run:analyze
aggregate the above count into the code review so we know how many hours the code review had in total.release_filepath
metric that averages the total number of code review hours per code review.rake run:results
that tests thisDo this in ActiveRecord, not straight SQL.