We have been working long and hard on 1.3 for some time, so it is time we show some screenshots showing how things will be different. I have chosen three screen shots to highlight our new approach:

1) Bank Reconciliation has been entirely redesigned in 1.3 with a new workflow and it is better designed to handle large numbers of transactions. Additionally you can go back later and review a reconciliation set to see what cleared and what was outstanding. This screen shot shows a report for a work in progress.

2) The contact management section is redone. Customers/vendors can now have multiple accounts, contact information, shipping and billing info, notes, etc. This screen shot shows how this looks with Javascript enabled. Here Javascript is used to clean up the interface, and the links at the top switch between visible divs.

3) The contact management screen also functions without Javascript. Here the links on the top are internal hyperlinks to the relevant container divs for the sections of the screen.

Ledger123.com has released a FreeBSD VMWare image with LedgerSMB 1.2.13 pre-installed.

It is available at their web site..

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.14 which is available from the SourceForge download page.

This release corrects a number of minor bugs including those relating to reporting, LaTeX templates, and the like.

Please click 'Read more' to view the change log for 1.2.14.

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.13 which is available from the SourceForge download page.
This release corrects all known issues with running LedgerSMB 1.2.x on PostgreSQL 8.3 and although other issues may surface, we will fix those as they are brought to our attention.

Please click 'Read more' to view the change log for 1.2.13.

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.11 which is available from the SourceForge download page. Some of these fixes are important for Canadian users, as it fixes some tax issues that are affected by the GST change.

Please click 'Read more' to view the change log for 1.2.11.

The LedgerSMB team is pleased to announce the release of LedgerSMB 1.2.10 which is available from the SourceForge download page.

The changelog for this release is quite long, please click 'Read more' for all the details.

Today is the first anniversery of LedgerSMB's first public release.

In the past year, we have released three major releases:

1.0.0: Major security enhancements

1.1.0 Moderate security enhancements, new features

1.2.0 Major security enhancements, new features.

In addition, each of these releases has had several revisions which have
corrected various bugs and security issues. All in all, we have had nearly
25 releases in a year. We have gone from 300-500 downloads in our first few
months to 800-1200 most months currently. While this is still only half of

Contributing to the LedgerSMB project with documentation and articles is easy. This short document will get you going in no time...

(From Chris Travers' post to LedgerSMB-devel list)

We have opted to release a milestone release on sourceforge with the changes towards 1.3.0 to-date. Please note that this release is largely aimed as a community update and is not suited well to either active development (due to rapid changes of the codebase) or for production use.

Highlights include:

• a new template system (Seneca)
• RESTful web services interface code (Jason)
• Normalized Contact Management schema to be basis for other CRM functionality (Josh D)

The LedgerSMB team is pleased to announce that version 1.2.6 was released on June 28th

The following issues have been corrected:

• customer_id field error in AP transactions
• invalid HTML in ca.pl
• Error searching for customer by address
• Error saving orders, projects, etc. with custom fields.
• Error saving project with NULL customer id.
• .po header information showing up on balance sheet.

Additionally, the following preventative measures were included:

• Meta tags were added to force the use of utf-8 by default