I was updating my codebase today when I noticed that for some odd reason, the file versions for scanner.module for 2.1 is actually older than 2.0-beta1.

2.1 has a version 1.3.2.1
2.0-beta1 has a version 1.4

And if you do a diff between both files, there are a lot of changes in each.

Was this intentional? Which is the correct file we should be using?

If 1.3.2.1 is the recommended file, I highly suggest you update it to 1.4.1 or something so that the version numbers accurately increment from the previous releases.

Thanks for such an awesome module!

Comments

aasarava’s picture

aasarava commented

Hi Linxor. The version numbers you're referring to are internal file revision numbers automatically inserted by CVS when I check in or tag files. I'm not sure why the 2.0 release was on the 1.3.x track rather than following the 1.4 track started by the beta -- it's certainly possible I checked things in out of order at the time, or that I changed my mind about the beta and made my updates for the 2.0 release in a different track.

But that said, the external revision numbers -- 5.x-2.0-beta1 and 5.x-2.0 -- are the ones to pay attention to when upgrading. I double-checked all the files and the 5.x-2.0 release is indeed the official release.

If everything works for you with 5.x-2.0, then use it! :) If not, let me know!

hargobind’s picture

hargobind
he/him
Location Austin, Texas
commented
Status: Active » Closed (fixed)