Version number in build scripts

[michelpons]

The Readme.txt file under trunk was made 19 months ago to explain how to develop a new version. It is not up to date. COBIA 1.2.0.10 has just been released, declared as released and a version 1.2.0.11 has been declared as the default version now in support tickets since any resolution of an issue will now be supported by 1.2.0.11, not 1.2.0.10.
When building COBIA distribution packages using the source committed since the release of COBIA 1.2.0.10, what is produced carries version number 1.2.0.10. It should be 1.2.0.11, partially to prevent binaries looking as 1.2.0.10 to be made public while they do not correspond to 1.2.0.10. Is it an update in Readme.txt that is needed, with inclusion of what should be done with script increaseversionnumber.py? Don't know but the project must be kept consistent.

[jasper]

In [321]:

Fix #142

[jasper]

In [322]:

Fix #142

[jasper]

In [324]:

Fix #142, Fix #143, added missing shared memory files, versioning libffi-cobia dlls, PMC creation unit tests setup (marshaled and unmarshaled), Test Unit PMC with custom types

[jasper]

In [00e2ed083f88008b1bfbbcc60bedc1bcff07f8cf]:

Fix #142

[jasper]

In [3d902f92e4bd9671ae76d38e5fc08ec3d4e43172]:

Fix #142

[jasper]

In [254b28a908fa9f30f021a1b09573a1f36a68374c]:

Fix #142, Fix #143, added missing shared memory files, versioning libffi-cobia dlls, PMC creation unit tests setup (marshaled and unmarshaled), Test Unit PMC with custom types