- devel - lists.freelock.com

LedgerSMB 1.7.0-alpha1 released
by Erik Huelsmann 20 Jan '19

20 Jan '19

Hi, After the merge of the (improved) Multi Currency Support branch (MC branch), we have released a preview version of LedgerSMB 1.7.0. It's not feature complete yet, but is intended as a general sense of direction for the 1.7.0 release and a way to solicit feedback. Note that you should run this version *only* on a *copy* of your database; this version is NOT intended for production use. The full changelog for 1.7.0 so far is included below. The most important feature by far is the improved multi currency support, which required quite extensive changes to the software. As such, this is the feature we're looking for feedback on most. If you need help getting set up to test 1.7.0-alpha1, please let me know! Changelog for 1.7 Series Forthcoming New functionalities * Deletion of template transactions (Nick P) * Transaction date now part of purchase history report (Chris T) * UI allows addition and removal of custom `account_link` flags (Nick P) Improved foreign currency support * Multiple rates per day per currency (Erik H) - Reversing a transaction from a closed-period on a day with different rate - Bank transfers with different banks on the same day with bank's fx rate - Migration from systems which support per-transaction or per-line fx rates * Multiple currencies in a single general ledger transaction (Erik H) - Posting an opening balance with all currencies in 1 transaction - Transferring between foreign currencies on e.g. Paypal in 1 transaction * Fixed copying of invoice copies fx rate without option to change (Erik H) * UI showing foreign and default currency amounts in transactions (Erik H) Quality Assurance * Expanded checks and resolutions for schema changes (Erik H) * Testing infrastructure and tests for schema change checks (Erik H) * Ensure correct dependency declaration (RequireExplicitInclusion critic policy) * POD documentation structure improvements, with automated checks (Erik H) * Expanded BDD tests, including payments, batches and approval (Nick P) Dependency updates * Dojo Toolkit (JavaScript UI tools) updated to 1.14.2 (Erik H) Code cleanup * Removed deprecated 'custom table' and 'custom field' tables (Erik H) * Reduce dependencies on deprecated LedgerSMB::App_State (Nick P) * Simplified deprecated LedgerSMB::PGOld (Nick P) * Remove unused LedgerSMB::DBObject and LedgerSMB::PGOld methods (Nick P) * Remove unused configuration settings in ledgersmb.conf (Erik H) * Further (compared to 1.6) reduction of warnings * Implemented tests for LedgerSMB::File(::*) modules (Nick P) * Template engine simplification by separation of UI and printed docs (Erik H) * Consistent copyright notices - with tests - on all Perl files in lib/ (Nick P) * Request handling cleanup by mapping 'flat' POST data into hierarchy (Erik H) Nick P is Nick Prater Erik H is Erik Huelsmann Chris T is Chris Travers -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.6.10 released
by Erik Huelsmann 20 Jan '19

20 Jan '19

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.6.10 * Apply correct layout to schema upgrade pages in setup.pl (Erik H) * Fix iteration over row data provided in schema data fixes in setup.pl (Erik H) * Fix schema upgrade with multiple failing checks looping infinitely (Erik H) * Improve wording of correction instructions of schema check failure (Nick P) * Respect tempdir when rendering ODS template (don't use current dir) (Nick P) * Add user feedback when invoice needs recalculation before posting (Erik H) Erik H is Erik Huelsmann Nick P is Nick Prater For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.10/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.10 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.10 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.10 These are the sha256 checksums of the uploaded files: 4028fcd2fd63d90988f031de013b81c4a11fe55b8908114e4c05f142ce6389a0 ledgersmb-1.6.10.tar.gz 071c780fc5d8e5b95f7009a86de8496a705e45496d3d9428bc7db25693244e26 ledgersmb-1.6.10.tar.gz.asc

1 0

MC branch merged
by Erik Huelsmann 20 Jan '19

20 Jan '19

Hi, After discussion on the LedgerSMB chat channel, it's been decided to merge the 'master-mc' branch. This means the MC changes will be in 1.7. Additionally, it means that quite extensive schema changes have landed on the 'master' branch. We're testing those changes with real-life databases to ensure good user experience upon release. We'd appreciate it if others want to join testing efforts of the 'master' branch and the new MC functionality. The current Changelog description of the merge is: Improved foreign currency support * Multiple rates per day per currency; from a single rate (Erik H) - Reversing a transaction from a closed-period on a day with different rate - Bank transfers with different banks on the same day with bank's fx rate * Multiple currencies in a single general ledger transaction (Erik H) - Posting an opening balance with all currencies in 1 transaction - Transferring between foreign currencies on e.g. Paypal in 1 transaction * Fixed copying of invoice copies fx rate without option to change (Erik H) * UI showing foreign and default currency amounts in transactions (Erik H) -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

What should the process toward merging the MC branch be?
by Erik Huelsmann 19 Jan '19

19 Jan '19

Hi, Over the past weeks, we (on the ledgersmb chat channel) have been working to complete all open tasks related to the "Phase 1" of Multi Currency support. Additionally, we have been testing the schema migration code with a number of real-life databases and fixing issues. A number of bugs and other findings have been fixed. Pre-migration versus post-migration trial-balance comparisons have been implemented as migration validations. The branch implements new tests unit tests and BDD tests. The branch implements tests for the schema migration code. The branch has undergone manual testing recently (in addition to the manual testing which happened when the code was written originally). The question now is how to proceed? Would anybody be prepared to jump in with manual testing of the branch and the migration code? Should we be merging the branch to master and find testers there? Should we be writing more tests on the branch before merging? If so, how many tests are "good enough" before we can merge? Or should we merge and develop tests on master? (Which we should anyway...) For anybody interested what it is exactly that I'm writing about, check the comparison between the master and master-mc branches: https://github.com/ledgersmb/LedgerSMB/compare/master...master-mc (statistics: 415 commits; 6417 additions, 3514 deletions, 161 affected files; first commit July 19, 2016; last commit: today.) Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 2

ledgersmb 1.6.9+ds-1 MIGRATED to testing
by Debian testing watch 01 Jan '19

01 Jan '19

FYI: The status of the ledgersmb source package in Debian's testing distribution has changed. Previous version: 1.6.8+ds-1 Current version: 1.6.9+ds-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information.

1 0

Release of Debian packages for LedgerSMB v1.6.9
by Robert J. Clay 29 Dec '18

29 Dec '18

An initial version of the Debian ledgersmb package for version 1.6.9+ds-1 has been released and uploaded to Debian: I anticipate it migrating to Debian Testing ("Buster") by next week (the announcement for which will be posted to the devel list) and also over to the current developmental Ubuntu version (which will be for v19.04). It has also been uploaded to our PPA[1] as version 1.6.9-1 of the ledgersmb-1.6 package: for 'cosmic' (v18.10) as well as 'bionic' (v18.04 LTS). (The Debian source packages are available as well.) The packages at our PPA: ledgersmb-1.6 ledgersmb-1.6-apache ledgersmb-1.6-lighttpd ledgersmb-1.6-nginx ledgersmb-1.6-varnish Only the main 'ledgersmb-1.6' package is required; the others are related to which web proxy you might want to use and you only need one of them. -- Robert J. Clay rjclay(a)gmail.com, jame(a)rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A. [1] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages

1 0

Release of ledgersmb-1.5 v1.5.24-1
by Robert J. Clay 29 Dec '18

29 Dec '18

An initial version of the debian ledgersmb-1.5 package for version 1.5.24-1 has been released and uploaded to our apt package repository for 'main' in stretch[1]. It has also been uploaded to our PPA[2], for 'cosmic' (v18.10) as well as 'xenial (v16.04 LTS) and 'bionic (v18.04 LTS). (The Debian source packages are available as well.) The packages at both our apt package repository and our PPA: ledgersmb-1.5 ledgersmb-1.5-apache ledgersmb-1.5-lighttpd ledgersmb-1.5-nginx ledgersmb-1.5-varnish Only the main 'ledgersmb-1.5' package is required; the others are related to which web proxy you might want to use and you only need one of them. Note also that 1.5.x release series will be supported up through December of 2019. -- Robert J. Clay rjclay(a)gmail.com, jame(a)rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A. [1] https://apt.ledgersmb.org/ [2] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages

1 0

LedgerSMB community overview 2018
by Erik Huelsmann 27 Dec '18

27 Dec '18

Here's my continuing the tradition to write about the state of the project on each year end. == Community interest == With the growth of the number of places to obtain LedgerSMB, it's becoming increasingly more difficult to estimate the project popularity. We're now available through at least the following channels: Distribution packages (Debian repository, Ubuntu ppa, our own Debian/Ubuntu repository), Docker images on Docker Hub (with docker-compose support), regular 'tar file' download through GitHub or our own download site. Many of these sources don't track stats for hits, or at least those stats aren't available to us. A notable fact though is that the Google and Yahoo searches 'open source accounting' serve as the top hits a number of pages which cite or refer to LedgerSMB. Based on the steady stream of issues being logged on our GitHub issue tracker, the fact that the number of forks and stars (as well as watches) are steadily growing and the number of Docker Hub downloads is steadily increasing, I'd say that we get a fair amount of attention and our community is continuing to find people interested. == Releases == Last year's community overview looked forward to 2018 and expressed the hope to release LedgerSMB 1.6 in the first half of the year. And we did: June 10th we released 1.6.0 -- little less than a 18 months after 1.5.0! As expected, we were able to further shorten the time between releases. This year, we haven't topped last year's 20 releases. With 20 releases, the year can definitely be called succesfull though. We released: - 10 stable releases: 1.6.0 - 1.6.9 - 10 old-stable releases: 1.5.15 - 1.5.24 Releases hardly ever contain fixes for regressions anymore. That's to say, regressions for functionality that worked in a recent release. Regressions being fixed went back to functionality being broken before 1.5.0 and sometimes even during the 1.3 or earlier release cycles(!). In addition to the 18 releases, significant new infrastructure landed on the master branch which helps advance the project to higher levels. An excerpt of all the work done includes further extension of the testing framework, separation of the template frameworks for UI and 'printed' materials and lots of minor and major code cleanups. In addition to generating releases, each year some effort is spent on release engineering; this year, we further automated the release announcements by automatically posting the news updates on github.com and ledgersmb.org (using the same announcement text as is used for the mail announcements). == Packaging and installation == The Debian+Ubuntu packages now include a new 'ledgersmb-1.6' package. The packaging process keeps improving, because by the end of the year, new packages were announced within 24 hours after the release of the new LedgerSMB version. With the introduction of the LedgerSMB 1.6 Docker builds, further energy was spent in shrinking the images. We started the year with images around 250MB in size (reported by Docker Hub); by the end of this year, images for 1.6 are showing less than 180MB and those for 1.5 around 160MB in size. That's another significant reduction. == Development progress == Over the course of 2018, 107 issues were created, of which 35 remain open at the end of the year (of which 8 enhancements); 126 issues were closed. More than 470 pull requests were created and 479 were closed. These numbers are significantly lower than last year, which is probably due to lower development activity (especially in the master branch) over the course of the second half year. However, the general feeling is that we are also continuing the trend of last year: due to the fact that the code base is increasingly more stable, there's more time to work on the more involved projects: those that (prepare to) refactor the code base. This work, while necessary, doesn't immediately produce commits or PRs. Last year, we set aside the code that we want to part with in the source tree, signalling to (potential) contributors which parts need improvement and which need replacement. Consensus has it that this distinction has lowered the barrier of entry by offering a relatively clean code base to newbee developers and this has in fact been a reason for this some of the activity of this year's contributors. In 2018, we ran over 1250 builds (starting at 6091; currently at 7354 and counting), but more importantly, we increased our test coverage from 27.48% to a current coverage of 34.22% (thanks Travis CI for all the donated compute time and Coveralls for the stats and analysis interface!). While we definitely have more code to cover to get to an acceptable coverage level, this is a very welcome increase! Areas which received extensive attention beyond that which has already been published through the 1.6 release notes include: - work to explore the benefits of moving our code base to Dancer2 - work to identify the roadmap to merging the MC (multi-currency) branch, including work to - re-implementing some of the changes on the branch to adopt new paradigms as on 'master' - implement checks, balances and tools to help people migrate their data to MC on upgrade - work to de-couple frontend and backend implementations, even before there is a web API - work to explore what needs to be done to support a REST API == New functionality and improvements == This year we added relatively little truely new functionality to the code base. Most effort was spent improving it. One thing worth mentioning in this area is the fact that we added tests to assert that modules (at the very least those we intend to keep) comply with a minimum level of documentation -- we set the documentation standard through Perl::Critic rules and we'll work toward increasing the standard over the next year, most likely. == Looking forward to 2019 == Ideally, we'll see the 1.7 release in the first half of 2019: that would shorten our release cycle to the much-desired yearly interval. Releasing by the end of the first half year puts businesses in a good position to test the software before running the year-end figures (assuming most businesses do so by the end of the calendar year). This year will likely be the year to land the MC branch effort on master, too. A lot of work has gone into preparation for this step and more work - following a precise checklist - is under way. Wether this functionality lands before 1.7 or after, is yet to be decided. Stability comes before anything else and we don't want to break our upward trend in that area. (Although some instability is to be expected after a subject this big lands on master, I'd like to have it stabilized before release.) For 2019, I wish the project finds one or two new contributors and our community has the patience to wait for MC to land before we continue into (also) highly desired areas such as a REST API -- to help the project to focus, that is. Then, lastly, let me finish by wishing everybody in our community a very good 2019 and by stressing that we'll welcome everybody who wants to contribute to our efforts (be it in development, testing, translating, documenting, coaching or sponsoring)! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

ledgersmb_1.6.9+ds-1_source.changes ACCEPTED into unstable
by Debian FTP Masters 27 Dec '18

27 Dec '18

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 26 Dec 2018 20:45:30 -0500 Source: ledgersmb Binary: ledgersmb Architecture: source Version: 1.6.9+ds-1 Distribution: unstable Urgency: medium Maintainer: LedgerSMB Core Team <devel(a)lists.ledgersmb.org> Changed-By: Robert James Clay <jame(a)rocasa.us> Description: ledgersmb - financial accounting and ERP program Changes: ledgersmb (1.6.9+ds-1) unstable; urgency=medium . * New upstream release. * Declare compliance with Debian Policy 4.3.0, no changes required. * Resolve issue with trailing spaces in the debian/changelog file. Checksums-Sha1: cd754b43b549513dbace45277a31515a4b6e7f62 3233 ledgersmb_1.6.9+ds-1.dsc efa19d0a485ff3b7795b8ce965fdedb6ad37d20e 1961328 ledgersmb_1.6.9+ds.orig.tar.xz a7842f3d0de0ce9e79a551569593e5809eb4c86a 35332 ledgersmb_1.6.9+ds-1.debian.tar.xz 368b7ebbc6893abf9e564d82ccce7c2a4cbadf79 10090 ledgersmb_1.6.9+ds-1_source.buildinfo Checksums-Sha256: 3c848a32198d80773679e1703f1eec8aefaf9cc87dc49451d2251585d9685636 3233 ledgersmb_1.6.9+ds-1.dsc 7e29702482dd84ab30caf176bbdf56b7069db488b36c921b4ff57878ab1b579b 1961328 ledgersmb_1.6.9+ds.orig.tar.xz 589a8ac6ad044168d33ae3038d29054762c320aedf15fc9b1a8f0534d8895f0f 35332 ledgersmb_1.6.9+ds-1.debian.tar.xz 5be9c327d0a049b3834fa4440a3818512773d42077e2e81d8d07bbdd5fbd0625 10090 ledgersmb_1.6.9+ds-1_source.buildinfo Files: e633cf6c5f229a43b8fc6bd3d2d56b39 3233 web optional ledgersmb_1.6.9+ds-1.dsc 1502debde292e73ab9e27e35c2f9fc23 1961328 web optional ledgersmb_1.6.9+ds.orig.tar.xz adf95697136a0b60fb950c5590d51401 35332 web optional ledgersmb_1.6.9+ds-1.debian.tar.xz ed85e66851e94e209a983a2bbb0f2bb4 10090 web optional ledgersmb_1.6.9+ds-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEJEg64IdNhpZtzez0GYyrb0O36poFAlwkOmYACgkQGYyrb0O3 6poccA/5AbT1ufSy4+hKHwamCxK/ruZuZwNQsid7KjbVYGq3wVFjkSo0d16li8C0 OwpPvdva4gQxkpbfRSe+8sunII+DArfGIXxKEnBta9/IfePjVYm7HPMDLHGwF6Z6 pOLaAJL2bIwQ4rCCw+wmmCSGxD6vOXnNRQTFFpsmgkhA7Q6AxC0vKgfDF3HSH6gu eNThG9lgVxayDMiHMjkofPZ1atw6XBtHbjYv4x7rPo48LC8bJ59G0YnTcGVh/ttc 4o88w3gC/4dbXlYoob3QNkvd8X89tyzVocbjPmmmLQzEpflMGpb/rgNkV3KW1xiq qb2TVe1zxOrJA/2542WVlkabXuo47mnUpOrePAZ3xjLPzg2tE2IsQ8We7Tr364qg lfCez5NLnaGM91kDdFM3W0VdKcU/HokZ9BlrwfCqI3cbyicYxMFwrAOTHFqziB55 lB+OrJRHGmfY61jk98wxMq+k1bON401LBkAmVAAJorA2DBnJm3jmOwuL9i6oebpc k+9vvGDentxrCGnqlWoGI38XoXPPHBM5+Xs6Wiq69eBQ2emdUB2FcKZtpyijChMx /Ym9azWTauxcndSUaay1Ii1HENsY8qua29jlhIBrKb3r3v1WA+fHyQ0pJi79HPqe +5riPyZS3M7K8baTM5EqXu+D6MVnmpGrMDo6ImtUwxLfx5kaNmg= =yxC1 -----END PGP SIGNATURE----- Thank you for your contribution to Debian.

1 0

Processing of ledgersmb_1.6.9+ds-1_source.changes
by Debian FTP Masters 27 Dec '18

27 Dec '18

ledgersmb_1.6.9+ds-1_source.changes uploaded successfully to localhost along with the files: ledgersmb_1.6.9+ds-1.dsc ledgersmb_1.6.9+ds.orig.tar.xz ledgersmb_1.6.9+ds-1.debian.tar.xz ledgersmb_1.6.9+ds-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

1 0