MapMan version numbers consist of four numbers separated by full stops (that's periods for the benefit of the American audience). For example: 2.10.5.0
| 2.10.5.0 | The first number will only change very rarely. A change to the first number represents a major project overhaul or rewrite. | |
| 2.10.5.0 | A change to the second number indicates a major new feature. | |
| 2.10.5.0 | A change to the third number indicates a minor new feature, major bug fix, or "clean-up" release containing several minor bug fixes. | |
| 2.10.5.0 | A change to the last number indicates one or more minor bug fixes or an administrative update. |
I don't always publish every version so gaps in the sequence of version numbers are to be expected.
On this web site I normally only quote the first three numbers, eg: 2.10.5 because the final number isn't usually significant. If I publish a new version in which any of the first three numbers change, then existing users are advised to upgrade at their earliest opportunity. This won't affect your licence status if you have bought a licence.
If only the last number changes then there's no real need to upgrade unless you are experiencing a specific problem which you know is addressed by the new version.
| Version | New features / bugs fixed |
|---|---|
| 2.13.1 |
|
| 2.12.1 |
|
| 2.11.4 |
|
| 2.11.3.2 |
|
| 2.11.3 |
|
| 2.11.2.6 |
|
| 2.11.2 |
|
| 2.11 |
|
| 2.10.15.3 |
|
| 2.10.15 |
|
| 2.10.6 |
|
| 2.10.5 |
|
| 2.10.1 |
|
| 2.9.0 |
|
| 2.8.0 |
|
| 2.7.0 |
|
| 2.6.0 |
|
| 2.4.0 |
|