Comment 10 for bug 681471

I'm still not 100% that this is the best way forward, but as a pre-implementation discussion for enabling the client to have all stats locally (as discussed above), we can:

1) Provide a command run a cron job with whatever frequency we like (4hrs?) that publishes the full statistics:
  * review_stats_all.json,
  * review_stats_changes_today.json
2) A second command for a cron job that runs daily publishing:
  * review_stats_changes_last_day.json
  * review_stats_changes_last_3_days.json
  * review_stats_changes_last_7_days.json

With these available, the client could always decide whether to grab the previous day, 3 days updates, 7 days or all the stats, depending how many days ago it last updated stats. I think that's a correct summary of mvo's idea?