summaryrefslogtreecommitdiff
path: root/doc/release_notes
blob: ca803b3355e997643c30da3b6bffa49f585c9823 (plain)
  1. RELEASE NOTES
  2. LedgerSMB 2.6.17
  3. 1: Welcome to LedgerSMB
  4. LedgerSMB is an accounting and ERP program initially aimed at small to midsize
  5. businesses. Currently the financials and supply chain management modules are
  6. fairly complete, while other modules such as project management exist in a
  7. rudamentary form. The initial features are identical to SQL-Ledger 2.6.17 from
  8. which it was derived, but it is expected that the feature set will diverge over
  9. time.
  10. 2: Differences between LedgerSMB and SQL-Ledger(TM)
  11. 2.1: Login name restrictions
  12. Logins in SQL-Ledger can contain any printable characters. In LedgerSMB these
  13. are restricted to alphanumeric characters and the symbols ., @, and -.
  14. 2.2: Session handling
  15. SQL-Ledger as of 2.6.17 uses session tokens for authentication. These tokens
  16. are based on the current timestamp and therefore insecure. Furthermore, these
  17. tokens are not tracked on the server, so one can easily forge credentials for
  18. either the main application or the administrative interface.
  19. LedgerSMB stores the sessions in the database. These are generated as md5 sums
  20. of random numbers and are believed to be reasonably secure. The sessions time
  21. out after a period of inactivity. As of the initial release both
  22. SQL-Ledger-style session ID's and the newer version are required to access the
  23. application. In future versions, the SQL-Ledger style session ID's will
  24. probably be removed.
  25. 2.3: Database Changes
  26. Under certain circumstances where the Chart of Accounts is improperly modified,
  27. it is possible to post transactions such that a portion of the transaction is
  28. put into a NULL account. LedgerSMB does not allow NULL values in the chart id
  29. field of the transaction.
  30. Also, the transaction amount has been changed from FLOAT to NUMERIC so that
  31. arbitrary precision mathematics can be used in third party reports. This ought
  32. to also allow LedgerSMB to properly scale up better as SUM operations on
  33. floating points are unsafe for large numbers of records where accounting data is
  34. involved.
  35. 3: Roadmap
  36. The project has no defined roadmap but rather a list of tasks and objectives
  37. outlined in the TODO list. There are many projects here and there are always
  38. room for new ideas.
  39. 4: Get Involved
  40. Contributors should start by joining the LedgerSMB users and devel lists. Code
  41. contributions at the moment must be committed by either project maintainer and
  42. should be submitted either using the patches interface at Sourceforge or the
  43. devel mailing lists.
  44. Additionally, we can use help in QA, documentation, advocacy, and many other
  45. places.
  46. SQL-Ledger is a registered trademark of DWS systems and is not affiliated with
  47. this project or its members in any way.