In the near future, we will start seeing a set of proposals for architecture changes between 1.3 and 2.0. These will be discussed and firmed up on the lists first, and then posted here after general consensus emerges.

LedgerSMB 2.0 is likely to be very different from 1.x. We plan to keep some of the decisions made in 1.3 but will move away from the current monolithic model.

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:

Changelog for 1.2.20
* Commented out credits in ledgersmb-blue.css
* Corrected encoding in Latvian chart of accounts (Janeks)
* Minor fixes to release notes (SF User akaihola)
* Exchange rate fix (SF User Anarcat)
* Fixed whitespace handling in admin.pl when saving permissions (Chris T)

Please note that this may be subject to change as we get more feedback from others.

I: Base Architecture Goals
=======================
The new architecture is designed to solve the following problems with the current codebase:

1) 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.

After reviewing a few problems from beta 2 and going through a rather
long list of patch submissions, we have LedgerSMB 1.3.0 beta 3 ready
to test.

This corrects (relative to beta 2):
1) Overly verbose logging (though this is configurable)
2) Errors saving customers/vendors and errors on bank reconciliation
3) Join projection anomalies in parts reports
4) New tests to avoid command line actions from causing errors with scripts.
5) Much more.

Enjoy!

LedgerSMB 1.2.19 has been released today which includes a number of
important fixes including the security hotfixes available. It also
includes a fix for a (rather rare) sales tax rounding bug where the
tax is sometimes rounded improperly when discounts are applied at the
same time. The complete changelog is:

Changelog for 1.2.19
* Fixed short sales with never-closed books (Chris T)
* Fixed erroneous tax rounding in POS screen (Chris T)
* Fixed XSRF vulnerability that allows changing user's password (Chris T)

Hi all;

It has been brought to our attention that a number of security vulnerabilities have been noted in SQL-Ledger. Several of these affect earlier versions of LedgerSMB, and three hotfixes have been released for problems that continue to affect the LedgerSMB codebase.

As always, we highly recommend testing all hotfixes before applying them to a production environment.

The CVE's mentioned here are the ones attached to SQL-Ledger. Subtle differences as to how these affect LedgerSMB are noted below.

These vulnerabilities include:

After a lot of hard work, LedgerSMB 1.3.0 is ready for beta testing. Please be aware that this is a beta-testing release and there may be unexpected bugs in places. Some things may not work as advertised. It can be downloaded from the sourceforge page (http://www.sourceforge.org/projects/ledger-smb/).

Known issues:
--------------------------

Hi every one,

first i want to congratulate you all for an excelente job.

My problem its that i want to translate Ledgersmb to spanish venezuela, I know that already it is, but here stell some words that there not, So i trying to do it in the same way just like "sqledger": perl locales.pl, but nothing hapen :S

Please anie help.

tanks.

harold.

[Chris Travers: All translation files are now in gettext's .po format. These can be found in locale/[country code]/