Telling version numbers from build numbersEdit
With Chromium, some uploaders of screenshots might note the build number only, which I believe should be discouraged, given that a version number seems better and more accurately to reflect the state of development of a particular branch. The reason is that with a version number, sorting files in categories and positioning them in galleries is easier. Including a build number is nevertheless welcome.
I do not know if Chromium versions match those of Google Chrome. Maybe it's not that important either.
Getting a proper version number for a particular build is not easy, so here are some possible options that should be used in concert with one another:
MAJOR.MINOR.BUILD.PATCH(formatting is somewhat different on a page). The accurateness regarding early builds (pre-alpha, and such) is inconclusive.
shows the date of the revision. It can match the image upload date.
This log page shows activities for a build up to a specified build number. The version number is broken down and most activities typically center on the "trunk version" or "trunk version build", which is the version seen in boldface at 4.0.266.0. To get the major version, one must scroll down and see what was specified in revision comments, which are written in free-form, so care should be taken when tracking a major version.
- omahaproxy.appspot.com offers extensive insight into very recent revisions (within three major versions in the works), but not older versions.
The version number should then be placed on the image page or supplied on the file talk page with one or more above links as sources.