There are two steps to upgrading a LedgerSMB 1.4.x - 1.11.x to 1.12:
The last step must be executed for each company database that's set up.
All versions from 1.3.0 to 1.11.16 are affected by a bug in Cost of Goods Sold (COGS) accounting for assemblies: Instead of accounting expenses and reducing inventory, negative expenses are posted, putting goods into inventory.
No. Only if you used assemblies in combination with LedgerSMB 1.3.0 through 1.11.15, you're affected.
There are two steps to upgrading a LedgerSMB 1.4.x - 1.10.x to 1.11:
The last step must be executed for each company database that's set up.
This content is outdated and kept here for reference only!
Company database upgrades are supported all the way back from 1.4 directly to 1.10, using the 1.10 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.9 structure, while upgrades adjust the existing structure for 1.10.
Company database upgrades are supported all the way back from 1.4 directly to 1.9, using the 1.9 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.9 structure, while upgrades adjust the existing structure for 1.9.
There are two steps to upgrading a LedgerSMB 1.8.x installation to 1.8.y (x smaller than y):
The second step has to be executed for each company database that's set up.
The steps to upgrade the software differ between Docker or tarball (from source) installations.
In case the installation was created using the docker-compose infrastructure provided by the project, the upgrade should be as simple as running
Company database upgrades are supported all the way back from 1.4 directly to 1.8, using the 1.8 software. Company database upgrades from 1.3 and 1.2 are also supported, but due to the different nature of the upgrade process are called "migrations". The important difference being that when doing a migration, a copy of the data is being created in the 1.8 structure, while upgrades adjust the existing structure for 1.8.
Short answer: Due to differences in the database schema in relation to storing foreign currency transactions.
Long answer: The database schema before 1.7 required 2 database rows in the acc_trans table to store functional currency and foreign currency amounts. As of 1.7, the schema stores these two amounts - which relate to the same journal line - into one database row. When migrating data from the old schema to the new one, the migration routine tries hard to identify pairs of rows which can be combined into a single row in the new schema.
There are two steps to upgrading a LedgerSMB 1.6.x installation to 1.6.y (x smaller than y):
The last step has to be executed for each company database that's set up.
Note that all the steps below are prefixed with the 'sudo' command, but these can be executed as 'root' directly as well.
This is by far the easiest part. These are the steps to go through, assuming an installation from tarball:
There are two steps to upgrading a LedgerSMB 1.5.x to 1.6:
The last step must be executed for each company database that's set up.