Agreed, some designers do leave out some of the dots.
But I would not like to assume that unless I had firm evidence and in this case there is none. Both the filenames and the Change Log text say “1.11” and “1.12”. So I would translate these to “1.11.0” and “1.12.0”.
Anyway, we don’t know for sure so you have to make your best guess. And as @uckelman says with 3000+ pages to move there is no time to fix errors.
There is evidence in this case that 1.11 and 1.12 are meant to be 1.1.1 and 1.1.2, respectively: You can’t consistently interpret what’s after the decimal point as a single version number component without having two releases with the same version, as you would have to read 1.1 and 1.01 both as 1.1.0.
To recheck:
Rechecking:-
Marita-Merkur - OK
Luzon: Race for Bataan - OK
Ivanhoe - OK
Italia 1917-1918: A Farewell to Arms - OK
Silent Victory: U.S. Submarines in the Pacific, 1941-45 - OK
La Trêve ou l’Epée - OK
La sombra del aguila - OK
In Their Quiet Fields II - OK
Dune: War for Arrakis - OK
Charioteer - OK
By Iron and Blood - OK
Bloody Tarara (TCS) - OK
Blockade - OK
Blitzkrieg!: World War Two in 20 Minutes - OK
La Vallée des Mammouths - OK
Le Dauphin et l’Epée - OK
La Bataille de Corunna-Espagnol - OK
Four Battles in North Africa - OK
Forgotten Legions - OK
Dixit - OK
Dien Bien Phu: The Final Gamble - OK
Case Yellow, 1940: The German Blitzkrieg in the West
Blackbeard - OK
Bismarck - OK
Battle Hymn - OK
Nachod and Skalitz 1866 - OK
Return to the Rock: Corregidor, 1945 - OK
The Fall of Tobruk: Rommel’s Greatest Victory - OK
Twin Peaks - OK
Lord of the Rings: The Confrontation - OK
A House Divided - OK
This page was misusing the file table headings. I’ve fixed it on the old page; this will get back into the queue for checking after the next wiki dump.
There are about 25 pages I’ve identified where there are a pair of modules for which their converted version numbers sort opposite to how they are intended to sort. The most common example of this is a module with version number 1.0 and a subsequent modification with version number 1.0a.
We’ve been converting old version numbers to be semver-compliant by making the trailing nonnumeric part the “prerelease” segment. (Semver versions are of the form X.Y.Z-prerelease-build, where everything after Z is optional.) In the case above 1.0 becomes 1.0.0 and 1.0a becomes 1.0.0-a.
The difficulty we hit with this is that X.Y.Z-prerelease sorts before X.Y.Z according to the semver rules—which means that 1.0.0-a sorts before 1.0.0 instead of after, as the module author intended.
It’s unclear to me at present what to do about this. Modules being assigned a semver-compatible version is a hard requirement, as is sorting in the correct order.
I feel that pre-releases should even have their own section perhaps on a dedicated development sub-page for the project from the get-go. Such a project - typically with multiple pre-releases - will have enhanced support requirements. Simply listing a project’s pre-releases in-line with normal releases is (I think) likely to sow confusion and clutters up the list of released versions.
Assuming, I’ve understood what the sorting issue implies for the module catalogue.
Could you possibly over-ride the semver sorting rules if, and only if, the “prerelease” file has a newer timestamp?
Another idea: add an automatically generated note to the new page disclaiming that the module sorting may be incorrect because the version numbers are not semver-compatible.
Yes, but I will not.
I’m considering ginning up version numbers that do sort correctly. E.g., BWN v1.1_rev.vmod is supposed to sort between BWN v1.1.vmod and BWN v1.2.vmod, and would if 1.1_rev were mapped to 1.1.1. Almost all of these cases are for modules which haven’t been current for a long time, so the chances of anyone even noticing the mismatch is low.
To recheck:
Many of these have some module with an adjusted version number.
Pendragon and River of Death look really good. 
Cheers,
Reg
It seems like we got in this state because Vassal accepted a free text entry field for versioning.
Given the desire to implement rigorous SEMVER, I would hope that the v4 editor would enforce the A.B.C-prerelease schema???
BTW - I would suggest given that v3 is likely to be used for awhile yet, it would make sense for the following… In v3, if a version number that is NOT compliant with SEMVER is entered, it pops a warning message to the module developer…
Yes, it will.
The new module library won’t accept upload of a module that has a noncompliant version number. That solves the problem I want to solve. I’m not inclined to do discretionary work on V3 at this point.
Rechecking:-
Imperial Struggle - OK
Raider Drop Zone - OK
Silver Bayonet: The First Team in Vietnam, 1965 - OK
Blue Water Navy - OK
Campaign Commander Volume III: Punic Island - OK
Death in the Trenches: The Great War 1914-1918 (Second Edition) - OK
Guild Ball - OK
Monty’s Gamble: Market Garden - OK
Nemesis: Burma 1944 - OK
Pendragon - OK
Polis: Fight for the Hegemony - OK
Quarriors! - OK
Remember Limerick! The War of the Two Kings: Ireland, 1689-1691 - OK
River of Death: Battle of Chickamauga, September 19-20, 1863 - OK
The Devil’s To Pay - OK
Queens’ Gambit: The War in Italy, 1742-1748 - OK
The Invasion of Russia (1812) - OK
The Killing Ground - OK
VCS Salerno - OK
Patton’s Best
Raid On St. Nazaire - OK
A Most Fearful Sacrifice: The Three Days of Gettysburg - OK
Amerika Bomber: Evil Queen of the Skies - OK
Age of Muskets Volume I: Tomb for an Empire - OK
BelTrain - OK
Demonlord - OK
The Speed of Heat - OK
Okko: Era of the Asagiri - OK
Kon-tiki - OK
Open Fire: Solitaire Tank Combat in WWII - OK
Case Yellow, 1940: The German Blitzkrieg in the West - OK
TINYforming Mars
The Burning Blue - OK
Futbol Extraño
1812!: War on the Great Lakes Frontier - OK
RRR - OK
This Accursed Civil War - OK
The Kaiser’s Pirates - OK
The Battle of Monmouth (1982) - OK
Silent War - OK
The Battle of the Bulge - OK
Star Wars: Armada - OK
Reds! - The Russian Civil War - OK
Red Badge of Courage
Next War: Poland - OK
Next War: Iran - OK
Pericles: The Peloponnesian Wars - OK
Outreach: The Conquest of the Galaxy, 3000AD - OK
Next War: Korea - OK
I’m now making a pass to fix files which are in the wrong releases or not in a release at all. This might take several weeks, as I don’t expect to have much availability over the holidays.
A bit of a conumdrum. 
The Freedom in the Galaxy module has two versions, a solitaire and two player variants. They are exactly the same except for player permissions and have been given the same version number (V2.05) by the author. The new library has assigned 2.5.0 tag for the solitaire file and has picked up the ‘two player’ phrase in the file name to make the other file 2.5.2.
I have done a bug fix in both these modules and was looking at how to identify these new versions with an eye on the upcoming library transition. As the changes do not affect gameplay or anything significant I was thinking of just making them both V2.05.1 which will work fine for the old library but appears incompatible with the new system.
Options appear to be to go to V2.5.3 & V2.5.4 to maintain an odd/even pattern for one/two player versions, or roll to 2.6.0 (or 2.6.1) for the solitaire and 2.6.2 for the two player to maintain compatibility with the current new library entry. The third option would be to split the entry into two packages with the same version numbers but I not aware that can be done yet.
Any suggestions?
Reg.