The LedgerSMB development team is very proud to release LedgerSMB
1.3.0. This release continues our strong commitment to security, data
integrity, and and robustness, introducing improved functionality in
many core areas, and adding new features that many businesses will
find necessary.
Hi all;
LedgerSMB 1.2.25 has been released. This code has been reviewed for a
the type of SQL injection issues recently reported and all
questionable cases addressed. While some cases are believed to be
exploitable, others have been fixed as a mere precaution.
SQL injection issues on 1.2.x should generally be presumed to be
severe unless we offer reasons otherwise.
Users 1.2.x are advised to upgrade as soon as possible.
Best Wishes,
Chris Travers
Hi all;
The LedgerSMB core team has released 1.2.24, which corrects three issues:
1.2.23 Release Candidate 1 is available on the Sourceforge file release site.
The complete changelog is:
Changelog for 1.2.23
* Fix for sales tax incorrect on sales/purchase order screen
* fix for unreadable characters in HTML templates in some charsets.
* Correcting backup name on backup by email
June 24, 2010
LedgerSMB 1.2.22 is available for download. This release corrects a few warnings and errors when Perl 5.12 is used, as well as some issues involving migrations between tax systems.
The complete changelog is as follows:
LedgerSMB 1.2.21 has been released. The complete changelog is as follows:
Changelog for 1.2.21
* Corrected a number of templates with HTML issues (Luke)
* AR/AP Aging Report fixed, ignores payment after report date (Chris T)
* Minor documentation updates (Chris T)
* Fixed bug saving SIC (Adam T)
LedgerSMB 1.2.20 has been released. You can download it at
https://sourceforge.net/projects/ledger-smb/
This release includes a number of moderate fixes. None of the fixes
are security-critical or critical regarding accounting data.
Changelog is as follows:
The new architecture is designed to solve the following problems with the current codebase:
A) Maintenance difficulty. The current codebase is quite unstructured and difficult to maintain. 1.2.x has already been a bit of a mess due to the issues of fixing something one place and having it break something else.
Since we never put forth a story describing what features and major changes have made it into 1.3 when feature freeze was declared I figured it would be a good idea to describe these here.