24th September 2020: PostgreSQL 13 Released!

LedgerSMB 1.0.0 Released

Posted on 2006-09-07

SQL-Ledger users, contributors, and members of the OSS community:

We have decided to launch a fork of SQL-Ledger in order to better serve our community. While I have been a strong opponent to forking our community in the past, I have reconsidered my position in the last couple of months. Our fork can be found at http://sourceforge.net/projects/ledger-smb/ and will be commercially supported by a number of community members such as Chris Murtagh, Metatron Technology Consulting (http://www.metatrontech.com), and Command Prompt, Inc. (http://www.commandprompt.com). It is a nearly seamless upgrade from SQL-Ledger.

We feel that the best way to help bring an open source accounting application to a larger group of users is to help provide what the community wants and needs. This includes open documentation and an open development system. Additionally, we have focused our initial effort on closing the most pressing issues of both security and data integrity as we feel that these areas have not received the attention they require. Our initial release makes the following changes:

1) Session hijacking bugs have been fixed both in the main application and the administrative interface.

2) acc_trans.chart_id now has a NOT NULL constraint, preventing orphaned portions of transactions when chart of accounts is badly set up.

3) acc_trans.amount is now NUMERIC instead of FLOAT, preventing roundoff errors either in third party reports or when large amounts of data are aggregated.

4) username.conf files are now generated on every login.

In addition, we pledge the following things in order to avoid the mistakes of the past:

-- LedgerSMB will be a real open source project with a public source code repository always;

-- LedgerSMB will have multiple developers, track bugs and accept patches according to standard OSS practice;

-- If our membership is accepted to Software in the Public Interest, we will work with this charitable organization to take substantive steps to prevent individuals or commercial parties from monopolizing the copyrights, domains, and trademarks of the project and the associated documentation.

We also have a long list of items that we intend to improve in this software and this work should keep us occupied for the foreseeable future. These improvements include new features, better security controls, and better data integrity controls.

We would also like to thank those who have contributed their ideas, feedback, and time to this fork. In particular I would like to thank Joshua Drake from Command Prompt, Inc. and Josh Berkus from SPI for their encouragement, contribution, and support.

Best Wishes,

Chris Travers and Chris Murtagh

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.