Page tree
Skip to end of metadata
Go to start of metadata


Version numbers indicate individual versions of a software in order to identify its further development in a comprehensible way.

A SmartNotes version is composed as follows:

A "new version" can therefore mean that there is a new annual version or a new "bugfix release", i.e. an error correction, for an annual version.

When you receive a new delivery, then ...

  • this means a "new (yearly) version" for you if the number for the yearly version has changed compared to the version currently in use.
    it means a "bugfix version" for you, if the number of the year version remains the same, but the build number is higher.

The diagram shows that the structure of the version has changed slightly from annual version 2.6 to 2.7. On the one hand the internal revision number has changed, on the other hand the build number is now sequential and can have three digits. Both are not relevant for you or the delivery process.


 When/why should we install a new bugfix release?

Since error corrections cannot be made in an existing version, they must be incorporated into a new bugfix version. To benefit from the corrections it is therefore necessary to install this bugfix version. If these corrections are not interesting for you, you can skip a bugfix.

 Should we install every bugfix release or can we skip a few?

Should we install every bugfix release or can we Basically, every delivery is first of all an offer and does not oblige you to install. If you can work with the version you are using without any problems, you are welcome to ignore a new delivery. You only have to consider that we cannot support the annual versions indefinitely. 

 When should we switch to a new annual version?

Switching to a new year version is always useful if you want to use the new features contained in this year version. 

 What does the note "If you are already using a higher version of SmartNotes, please ignore this mail. "

We inform all customers about the release of a new version with a delivery e-mail. Since we usually do not know the version you are using, you must decide whether an update is relevant for you. If you are using a higher version (e.g. 2.7.9.51) and receive a delivery mail for a version 2.6.0.36, then this update is not relevant for you because you should not switch to an older version.

 Why is there still a new release for the annual version 2.6 although there is already the annual version 2.7?

Even if a new annual version is available, errors in the previous year's version are still corrected and made available as a bugfix release. The internal processes for software updates are different in many companies. Often it is only possible to install an annual version once a year, whereas a bugfix release could be installed several times.

 Which one is better? The first delivery of an annual version or the last bugfix release for an annual version?

Since we only include new features in the annual versions, this version unfortunately contains more potential sources of error. Of course each of our deliveries is subject to extensive testing and will only be made available if these tests are successful.  However, especially with new features it can still happen that we do not find errors. This may be because our tests still need to be optimized or because the new features are used differently than we had imagined.

Since a bugfix release only contains bug fixes, the last bugfix release of a version is necessarily the bug-free one.


 Can I also skip a year version and e.g. change directly from version 2.6 to 2.8?

Yes. Whichever version you want to switch to. The server and client components are always reinstalled. Only the database needs to be updated. Therefore you have to execute all scripts which are between the current and the target version. 

 Which versions are the latest?

The annual version 2.6 as Release 2.6.0.36

The annual version 2.7 as Release 2.7.9.93

The annual version 2.8 as Release 2.8.1.18

  • No labels