sumex1.net  -  the site for software
developers using Sumex I+ products
versioning definition  ·  propagated versions
 
current active module versions
 
home
system
integrators
search the
site
 

validator
modules
invoice
modules
credit
modules
miscellaneous
modules
tools

  Design by TMR AG
  © by sumex1.net
 
How the versioning is handled...

All COM modules of the SUMEX I+ project are handled the same way regarding the versions. The basic format of a version is as follows:

Major_Interface_version.Minor_Interface_version.Build_number e.g. 2.04.008

Note that the minor version and build number are always given as a 2 digit and 3 digit number respecively.

This versioning scheme reflects dependencies of the COM modules towards the principal software using this module.
Change of ... Meaning/Dependency
Build number internal bug fixes, updates
Software developers
No need for software developers to change anything in their software.
The new version is announced for download via web site and mailing list at the same time when the new version is integrated into the netUpdate space.
End users
Next time the netUpdate is run the new version of the COM component is downloaded, updated and activated
Minor_interface minor change in the interface. New features are added but there are no changes in existing methods such that the compatibility is compromised.
Software developers
Software developers can change their programming to take advantage of the new features. But there is no ultimate need to do so, as the new COM component runs as well with unchanged software.
The new version is announced for download via web site and mailing list some weeks before the new version is integrated into the netUpdate space.
End users
Next time the netUpdate is run the new version of the COM component is downloaded. Since the naming of the component includes the major and minor version the "old" version is not overwritten but is coexisting to the new one. If the principal software is upgraded as well (loading the new COM component), then the new features are activated.
Major_interface major changes of the interface. Due to e.g. legal demands the behavior of the COM module must be changed. Backwards compatibility is not given by definition!
Software developers
Software developers must change their programming, the new component is not backwards compatible with the legacy system. Major interface changes are only undertaken if there is a legal external demand.
The new version is announced for download via web site and mailing list some months before the new version is integrated into the netUpdate space.
End users
Next time the netUpdate is run the new version of the COM component is downloaded. Since the naming of the component includes the major and minor version the "old" version is not overwritten but is coexisting to the new one. As soon as the principal software is upgraded as well (loading the new COM component), then the module is activated.