Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
https://www.drupal.org/project/usage/2638078
States that the release has had 68 installs by the time the scripts ran on December 12, 2015.
However, that release was made a week after that date on December 19th, 2015:
https://www.drupal.org/node/2638078
Comments
Comment #2
drummI made this mistake last week too. Read the header on https://www.drupal.org/project/usage/2638078 closer, the header is “Week starting”
See also #2365767: Usage statistics pages are not clear about start/end dates.
Comment #3
markhalliwellOk, so maybe it's not an entire week, but the logic behind this still isn't right.
The next "Week Starting" would be Dec 19th. So for the Dec 12th week starting, it should have ended on Dec 18th. The release I made still shouldn't be added to this week since it was created on: December 19, 2015 - 07:28 (https://www.drupal.org/node/2638078).
There's also the fact that these scripts actually run on Sundays and not Saturdays. So the definition of what "Week Starting" actually means is still unclear.
Comment #4
drummThe dates are rendered from timestamps using Drupal’s
format_date()
, with the current user’s time zone. The timestamps are midnight UTC, so they will be different depending on your hemisphere. And then the rendered HTML for the whole table is cached, so they are different depending on who requested the page that got cached.Adding a timezone parameter to project_usage's calls to
format_date()
should clear this up.Comment #5
drummComment #6
hass CreditAttribution: hass commentedIf I read Recent release usage and there is a date, than it is not mentioned that this means Week Starting. It looks more like - on day X it had counters X.
Showing a usage of 21 installations on date Jun 5, 2016 and I have released a module version on Jun 9, 2016 first is more than confusing.