Stable Releases are published every few months, once the product accumulates several meaningful Changes.
For instance, on the figure below, examples of Stable Releases are 3.0.1233 and 3.0.1234.
Please note that the figure shows only two changes between Stable Releases for illustrative purposes, whereas in reality, the number of changes will be higher.
Each Stable Release undergoes a rigorous automated testing procedure, actually ensuring its stability. Moreover, the development methodology takes into account configuration,
API, and DB schema backward compatibility.
We strongly recommend that every client upgrades to the current Stable Release, even those clients who believe "everything is working well, thank you."
Why? Firstly, this allows clients to receive fresh defect and vulnerability fixes. Secondly, clients benefit from new features and improvements to existing ones.
The actual Stable Release (3.0.1392) is available on our website's front page,
and you can find the accompanying changelog here.
Additionally, you can always seek recommendations from your assigned Consultant, who can provide an overview of all the new features and improvements found in the new Stable Release.
A change is a code modification identified by a unique number (23456 and 23422 in the Figure below), which can involve either a 'fix' for a defect or a 'feature' addition.
While Stable Release numbers must be sequential, Change numbers do not necessarily follow this pattern, as different developers can work on the development of several changes in any order.
It is also possible for multiple changes to be developed simultaneously. Each code modification within a change is accompanied by a release, as shown in 3.0.1234.23456 and 3.0.1234.23422
in the Figure below. These releases containing changes are published in the the catalogue.
Updating to a "Change" build allows clients to quickly integrate new functionality into their BGERP installation.
Such updates can be performed by navigating to Administration / App / App status interface snap-in and using Update on change item.
This procedure is typically used by change requestors (clients who have requested a specific feature or fix).
00000 Pre-Stable Release
Documented changes that have undergone unit or limited integration testing are accepted into the product as part of a pre-release release 00000. This release is used for:
- New installations;
- Trial installations used for new feature discovery or testing;
- A Demo System;
- Test/Pre-production server updates until a new Stable Release becomes available.
It is important to note that updating to any "Change" build inherently means acquiring all the features of a 00000 Pre-Stable Release,
effectively adding that specific change to it. The 00000 Pre-Stable Release will receive all product fixes,
allowing clients to access them before the next Stable Release, which, as mentioned earlier, is published every few months.