The 7.x dev releases for the Publication Date module are conspicuously missing from the module's usage statistics. I myself have been running the 7.x-2.x-dev release on a site the has the Update module active, so at the very least I would expect to see my installation in the logs. I've also noticed a sharp decrease in module usage since the last dev release and now I'm suspecting at least part of this may be people switching to the dev release and not being counted.

Comments

drumm’s picture

drumm
he/him
Location NY, US
commented

I think http://cgit.drupalcode.org/publication_date/tree/publication_date.info needs

version = "7.x-2.x-dev"

Otherwise, there is no way for Drupal to know the version when the module is run directly from Git.

In the tarball, there is

version = "7.x-2.1+11-dev"

I think that will be counted with 7.x-2.1.

jstoller’s picture

jstoller
he/him
commented

So, the .info file will have two version declarations? Is this documented anywhere? It seems like a bug to me. I would expect that 7.x-2.1+11-dev could be recognized as 7.x-2.x-dev. Or, if that's too difficult, then why wouldn't 7.x-2.1+11-dev be listed as its own version? It might mean a significant increase in the number of versions listed, but at least it would be accurate.

drumm’s picture

drumm
he/him
Location NY, US
commented

So, the .info file will have two version declarations? Is this documented anywhere?

I double checked this, and it is indeed documented that I was wrong about including a version in the .info file as checked into Git, https://www.drupal.org/node/542202. (It is something core is okay with in D7 and lower, values further down in the file replace others.)

That said, update module needs some source of version information for Git checkouts. Either Git deploy module, or drush make doing its own .info file additions.

drumm’s picture

drumm
he/him
Location NY, US
commented
Title: publication_date-7.x-2.x-dev does not appear in usage statistics » Versions like '7.x-1.0+10-dev' might not be counted for '7.x-1.x-dev'
Project: Drupal.org infrastructure » Project
Version: » 7.x-2.x-dev
Component: Updates System » Usage statistics

I do see a likely bug in our usage stat processing. http://cgit.drupalcode.org/project/tree/usage/project_usage.drush.inc#n270 looks like it uses the version from the URL directly, so those versions would not be counted.

If $qdata['version'] matches the 7.x-1.0+10-dev format, it should be rewritten to 7.x-1.x-dev.

jstoller’s picture

jstoller
he/him
commented

For what it's worth, the module on my site was installed via drush and I've confirmed that .info contains the information added by the Drupal.org packaging script, including the version string.

; Information added by Drupal.org packaging script on 2014-12-12
version = "7.x-2.1+11-dev"
core = "7.x"
project = "publication_date"
datestamp = "1418349482"
jstoller’s picture

jstoller
he/him
commented

I was poking around, and found a number of other modules on D.O. that have dev releases represented in their usage statistics and I don't see anything different about their .info files. What's the difference between my Publication Date module and, say, the Display Suite module?

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Status: Active » Fixed

This was fixed as a part of larger usage stat processing updates

http://cgit.drupalcode.org/infrastructure/tree/stats/fastlyusagestatpars...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.