The LedgerSMB team is considering a potential breaking update in the fall of 2026 or early 2027. For the sake of this email we will be calling it the 2.0 release, but we might decide to name it 1.14. By breaking update we mean that significant changes are being made to the database schema and supporting code. We expect automatic migration to work for all users of the latest 1.13.x as of the 2.0 release date. Older versions will probably need to update to 1.13 latest before the 2.0 upgrade can be applied. The Problem The old code prior to 1.13 had several undocumented and potentially broken code paths, the most researched has been related to overpayments, but there are others. We think we have handled these rarely used code paths. However we cannot be sure because it is not clear how users may have been using LedgerSMB. In the next releases, which should be, 1.12.19 and 1.13.6 we have included code to detect whether or not automatic code migration will work correctly during the 2.0 update. We need users to run these tests in setup.pl against their production database backup and let us know the results. This will help assure that we have time to correct any oversights in the auto migration before the 2.0 release. This is just a heads up notification. The next 1.12.x and 1.13.x releases will include detail instructions for this troubleshooting. Additionally, please note that we have upgraded the LedgerSMB Matrix room. You may need to resubscribe at https://riot.im/app/#/room/#ledgersmb:matrix.org. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.