What's new in LedgerSMB 1.13

This release features, among others:

• ...

Be sure to check the UPGRADE NOTES below! When upgrading from 1.10 or earlier, please read the 1.12 release notes.

New features

Feature 1

Description 1

Note for upgrades: Note 1

Notable changes

Change 1

Description 1

Note for upgrades: There are no consequences for upgrades.

Upgrade notes

Deprecated support for "ledgersmb.conf"

Please convert your "ledgersmb.conf" file to "ledgersmb.yaml". The current release supports it, if forced, by setting the environment variable "LSMB_FORCE_LEDGERSMB_CONF=Y"; however, as of 1.14, the INI based configuration will entirely be dropped. (The "ledgersmb.yaml" approach has been supported since 1.10, released in autumn 2022; 1.13 will be supported until 2027, giving ample time to switch.)

Background: The YAML system provides a lot more flexibility for the configuration of system components. It features a concept called "Dependency Injection", allowing a much broader range of configuration changes than the ones planned ahead of time by the developers as was supported by the INI based configuration.

Upgrading from SQL Ledger

Upgrades are supported for SQL Ledger versions up to 3.0. The project aspires to support migrations for SQL Ledger up to and including 3.2.12 and is looking for real-life data to build and test these migrations.

Background: Building a data migration from an accounting system to another is a non-trivial effort, even if accounting data looks the same in all of them. The project set high standards for the quality of every aspect of the software. After all: this is your accounting data! In order to deliver sufficient quality migrations, real-world test data is an absolute must-have before release; almost always there are functionalities hidden in the database data that can't be seen from the database tables and indexes alone.