- devel - lists.freelock.com

Call for translations / preparations of 1.7.0 release
by Erik Huelsmann 28 Aug '19

28 Aug '19

Hi all, With LedgerSMB 1.7.0-beta1 out for nearly 2 months now and without significant findings so far, the project team has started the final release process. This mail is both to announce that we're expecting to release 1.7.0 in a few weeks as well as a request for contributions: if you would like to donate to our community and don't know how? Translating LedgerSMB to a language you know will be of great help! Getting started with translating is as easy as creating an account on Transifex (https://transifex.com) and joining the LedgerSMB project there ( https://www.transifex.com/ledgersmb/ledgersmb/dashboard/) Your updated translations will automatically be included in all releases where applicable (from the latest 1.7 to any releases further 1.6 and 1.5 releases yet to come). The 1.7 release mainly features multiple currency rates per currency per day. Other development effort has been spent in building more tests so that test coverage has increased from 29% at the time of the 1.6.0 release (May 2018) to 41% on the 1.7.0-beta1 release. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.6.11 released
by Erik Huelsmann 18 Aug '19

18 Aug '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.11 * Add CSS indentation to hierarchical financial statements (Erik H) * Fix random setup.pl errors due to assumed-available credentials (Erik H) * Fix failure in setup.pl when initial user exists in the database (Erik H) * Fix SQL Ledger version-comparisons when upgrading to LedgerSMB (Yves L) * Fix regression when running in a schema other than 'public' (Erik H) Erik H is Erik Huelsmann Yves L is Yves Lavoie For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.11/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.11 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.11 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.11 These are the sha256 checksums of the uploaded files: 61d41b0ba75c80ce99108b0c6bdf06d9f9b95833397ecb29b6dea087c70a8b67 ledgersmb-1.6.11.tar.gz b525207d5fdd23f325e08059c155293b1fc3e0ab26b6d98efff77328dc2ef273 ledgersmb-1.6.11.tar.gz.asc

1 0

LedgerSMB 1.5.25 released
by Erik Huelsmann 18 Aug '19

18 Aug '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.5.25 * Fix regression when running in a schema other than 'public' (Erik H) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.5.25/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.5.25 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.25 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.25 These are the sha256 checksums of the uploaded files: 60bf5520a10f870d5c9f2b0ce620262f376fcc986011d6e00fc21ac6e8fd87a0 ledgersmb-1.5.25.tar.gz 369da04c42cb94888e48b4db3c41a2f376ae5fbd9695041bcfee14d7d3173eba ledgersmb-1.5.25.tar.gz.asc

1 0

Dancer2 vs Plack::Request+Router::XS+Middlewares+TemplateToolkit+Beam::Wire ?
by Erik Huelsmann 06 Aug '19

06 Aug '19

Hi, Last year, I started experimenting with Dancer2 (one of the options on the table for our target framework when we rewrite much of our code). Today, I've been updating that code to the HEAD of the current master branch. During the work I've done so far (last year and today), I've come across several obstacles which now lead me to bring up the following for discussion. So, let me start by stating which problem I think we're looking to solve: we need a means to do request parameter handling, session management, pluggable authentication, routing, management, template handling and abstraction of a templating library. During my experiments with Dancer2, I found that indeed it provides a framework with the desired properties. However, as with other frameworks, Dancer2 imposes its "framework structure" on applications. Normally this helps simplify the task of application development. Yet with the peculiarities in our code base, I'm finding that to implement required functionalities, I'm already working against the framework rather than with it: 1. Session management (cookies) As part of the move from our current design to the Dancer2 framework, I'm aiming for setup.pl and login.pl to become completely separate applications, meaning that they require separate authentication cookies (to allow separate, concurrent logins into both apps from a single browser) While Dancer2 does support multiple apps running on a single instance of its framework (such as required to run login.pl and setup.pl from the same backend), it doesn't support - in its configuration file (config.yml) - that these apps use disjoint session management cookies. In order to support this use-case, I've had to add request hooks, changing the name of the session cookie on a per-request basis. 2.Pluggable authentication As LedgerSMB uses a rather unusual authentication scheme where the user+password+database name are required for login, our authentication scheme doesn't fit the standard set by the framework (Dancer2::Plugin::Auth::Extensible::*), I've ended up hacking "deep" into the internals of auth::extensible: our authentication couldn't be achieved without replacing the login templates and finding ways to make more parameters available than supported out of the box. 3. Templating library abstraction While abstraction from templating libraries sounds nice, in practice it's cumbersome to switch templating libraries: on the Perl side the abstraction works fine to swap from one to another, but templating libraries usually use different templating "languages" (i.e. TemplateToolkit uses different directives and paradigms than XSLate). So, it seems that managing instantiation of the templating library is more important than abstracting it. 4. Route definition & dispatch With the ability to define routes, we'll be able to detach URL structure from our internal code structure. Dancer2 has a nice DSL to support the definition of routes for non-webservice entry points. There are plugins available to extend the DSL with convenience keywords for definition of webservice entry points. However, the syntactic sugar provided by the endorsed plugin (Dancer2::Plugin::REST) provides 1 new DSL keyword which is nothing more than a way to attach 4 functions to a resource (create, get, update, delete) providing a generated route for each; I see very little benefit to this plugin. In addition, this plugin doesn't support HTTP's content negotiation; instead, it expects the requested resource to have an "extension" to indicate the desired response encoding (e.g.: /users/1.json returns JSON, /users/1.xml returns XML, etc). This isn't "http-native" enough for me and thereby unacceptable for our use. Then there's the (not endorsed) Dancer2::Plugin::WebService; however, this too encodes the desired response encoding in the URL... 5. Framework configuration Dancer2 supports running multiple "apps" on a single instance. We want to run multiple apps: our setup.pl and login.pl. Even: we want these multiple apps to run on different authentication domains (i.e. when a user is logged in in /login.pl, we don't automatically want the user to be logged in into /setup.pl too). During my experiments I found that this isn't something that Dancer2 supports in its configuration: it can be "tricked" to support it by installing the correct pre- and post-request hooks in the framework, but out-of-the-box, it's not there. I'm not sure what other areas this will affect in the future, but from the structure of the configuration, I'm imagining it'll be an issue in many places. So what is our way forward then? Well, while we were working to merge the Multi Currency branch and stabilizing the 1.7 release (this process is still on-going), I've been looking around for solutions to these issues and I think the Perl library ecosystem has very nice options for almost all of the problems mentioned above, with the remark that there will obviously not be such a nice DSL as there will be with Dancer2. The following alternatives are available: 1. For session management using encrypted cookies, there's Session::Storage::Secure which works and is agnostic of underlying technology 2. For pluggable authentication, as we need to write our own authenticator anyway (and we actually already *have* that as a Plack middleware), I there's no effort if we can reuse that 3. For templating engine abstraction, well, I guess that with my line of reasoning above, there's little reason to have abstraction for templating engines at all (I mean, there *is* for a framework which needs to support many code bases, but there isn't for our specific use-case: our code base) 4. Route definition and dispatch (including extraction of route parameters) is available in a technology agnostic library Router::XS; while this library doesn't have the solid DSL that Dancer2 has, I'm expecting us to move more and more to Webservice entrypoints (either JSONRPC, GraphQL or REST) meaning that the DSL Dancer2 provides will be far less useful as stated above 5. Framework configuration could be handled through one of the regular YAML libraries, but even better - especially with inversion of control / dependency injection - we could turn to Beam::Wire and be able to deal with the most complex configurations by deferring configuration handling to sysadmins Obviously, Dancer2 will be able to do request parameter handling. That's something that's supported today too: we already have Plack::Request to handle parameter parsing (both URL and body parameters). So, after this long story, I'm wondering if moving to Dancer2 is worth it, or that we can simply stay on Plack with its middlewares and put the aforementioned modules to good use. Lets have your opinions and a good discussion on the matter so we lay a strong foundation for next steps for our project. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 4

Test coverage milestone
by Erik Huelsmann 21 Jul '19

21 Jul '19

Hi all, Roughly 4,5 years after the first coverage test run (12 September 2014) and little over 3 years after the first BDD test runs with coverage testing, on April 12th, we have finally reached the 40% coverage milestone demonstrating the effectiveness of the BDD tests to increase coverage. To get to this point, we contributed to or even created various other Perl project: * Test::BDD::Cucumber (bugfixes, plugin-capability, "prove" integration) * Weasel (Web-app and Single Page App testing) * Pherkin::Extension::Weasel (Weasel integration with Test::BDD::Cucumber) The most recent addition here - added in March - was the ability to generate an HTML log with screenshots of the web session; for an example of such logs, including screenshots of the application after execution of the various test steps, see https://132-18471236-gh.circle-artifacts.com/0/tmp/artifact/logs/index.html All of these contributions helped to accelerate the release schedule of LedgerSMB with fewer reported new issues on each release. With the size of our current test suite, we were running into limitations of Travis CI, with our test suite now approaching maximum run time for a test job. Over the past months, we've therefore been working to move part of our test suite to CircleCI. As part of this migration, we've been confronted with many timing issues which made our test suite produce more than acceptable false-negatives (but never false positives, fortunately). We've addressed all known instability issues now and moved testing of our master branch to run both on TravisCI and CircleCI. Our test coverage measurements (the slowest part of our tests) is produced on CircleCI and published on Coveralls.io ( https://coveralls.io/github/ledgersmb/LedgerSMB?branch=master) With the improved testing in place, I've been able to clear my backlog in old and pending changes. In the immediate future, new releases of Pherkin::Extension::Weasel and various Weasel::* modules are to be expected -- improvements to further help developer efficiency. Apart from work on expanding the test suite itself, Yves and I are likely to start moving our test suite from 'prove' to 'yath' ( https://metacpan.org/pod/distribution/Test2-Harness/scripts/yath) because it deals with UTF-8 from the start, where we're currently seeing warnings from 'prove' relating to UTF-8. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

migration from App X
by Andre Steenkamp 02 Jul '19

02 Jul '19

Hi Folks, I'm a LedgerSMB noobie. I have installed LedgerSMB and Postgres in Docker successfully (using docker-compose with modified yml file) with port 5432 open to the db so I can address the Db directly. The install works as expected (just had to set users passwords twice). What I would like help with is either some code to migrate from Sage to LedgerSMB or just some code or point me to some docs to get me started, please - I'm fluent in Java, some C++ and its been about 4 years since I seriously coded in Perl. -- *Regards,* *Andre Steenkamp* Primal Factors Consulting MBA International Business Bsc. Computer Science / Engineering SA Mobile: +27828781465 USA Mobile: +12627325285 Skype: andre.steenkamp

1 0

LedgerSMB 1.7.0-beta1 released
by Erik Huelsmann 01 Jul '19

01 Jul '19

Hi, After the release of 1.7.0-alpha1 we have been working towards the 1.7.0 release as described in our community update. We feel that the 1.7.0 branch is feature complete and while we're developing tests to find and fix possible regressions and older bugs, no new features or major changes are expected to be implemented before 1.7.0. This means that the current code base (modulo any and all regressions we can find and fix) will become 1.7.0 when it's ready. To help you find the bugs we need to fix before the release, we have published 1.7.0-beta1. It's available as a Docker image from Docker Hub under the tag "ledgersmb/ledgersmb:1.7.0-beta1". See https://hub.docker.com/r/ledgersmb/ledgersmb/builds/ Additionally, the release can be downloaded as a tarball from the download site: https://download.ledgersmb.org/f/Beta%20Releases/1.7.0-beta1/ Please report any issues you find in reply to this e-mail (that is, to the mailing list) or create an issue on GitHub with your finding: https://github.com/ledgersmb/LedgerSMB/issues/new?template=ISSUE_TEMPLATE.md -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB community update
by Erik Huelsmann 01 Jul '19

01 Jul '19

Hi, It was just before New Year when I sent out the last community update, so it's time for a follow up. This half year, we only released 1 maintenance release for 1.6.10. With no specific new bug reports coming in, the development team was able to focus its efforts on 1.7.0. On that front, a lot of development effort has gone into getting the Multi-Currency branch ready to be merged to master. On January 20th the long-awaited multi-currency branch merge happened, followed by the release of 1.7.0-alpha1. Since then, we've been developing more tests simulating user interaction with LedgerSMB to ensure that 1.7.0 will be as good as 1.6.0 when it is released. In the process, we have been fixing a few regressions. With the additional tests - which include tests for AR & AP invoices and transactions - we have increased test coverage from 29% (current on 1.6) to 40% (on master) and we're working to increase the number to well above 50% before release. The speed at which we're able to implement new tests is severely impacted by the fact that we hit a continuous integration limit: Travis CI allows us to run tests for a maximum of 50 minutes. Our test suite runs between 40 and 45 minutes in code-coverage testing mode. A lot of effort has gone into working on this problem. We're working to off-load the code-coverage test jobs to another Continuous Integration service (CircleCI) which *does* allow jobs to run longer than 50 minutes. Another direction of research was to reduce execution time of our test jobs. And while that did turn up some bugs in our Selenium test driver, it mainly helped the area where we didn't experience any problems (the non-code-coverage tests were reduced from 29-30 minutes of execution to 20-21 minutes of execution). Migrating some of our test infrastructure to CircleCI turned out to have the additional benefit of being able to start running our tests against Chrome and Firefox. Currently we only run against PhantomJS. While PhantomJS implements enough of JavaScript to support our testing, it's unmaintained and getting behind on recent standards. Being able to test with Chrome and Firefox will help to take advantage of more modern browser development techniques. As part of our optimization work, we helped create new releases of Weasel, Pherkin::Extension::Weasel and Test::BDD::Cucumber, where significant new features were added to Pherkin::Extension::Weasel to support increased developer efficiency. Looking to the immediate future, we're expecting to release 1.7.0-beta1 this week: we think 1.7.0 is feature complete and we'll work simply to stabilize it from here on. This means that 1.7.0 isn't production ready, but we're looking for people to test-drive it and value any and all bug reports we can get! Regards, Erik. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

I have been held up when I discovered the lack of Docker in OpenBSD
by Chris Bennett 12 Apr '19

12 Apr '19

Hi, I've kinda disappeared for awhile because OpenBSD does not support Docker. Just as I was ready to get started, I ran into that problem right away. I have meant to send an email about that, but I was rather frustrated with the problem. I also intended to help with the Spanish translations. And didn't. The good news on that, I did find a Spanish/English dictionary specifically for business terms only. That's not a book I expected to find, much less expect to exist. As far as OpenBSD, I need to do lot of work on that. Could someone recommend a Linux distribution that works well that I can install and look at as an example as I work? What is the situation with browsers? I use mostly Firefox, but I'm finding more and more sites that really run off of only Chromium properly. Where are the right repositories located for development at? OpenBSD is running PostgreSQL 10.5 (or later when -current is released soon). Any issues with that or later versions of PostgreSQL? I discovered that some work was started on Docker by someone else quite a while back, but has not been worked on any further. I'm a little bit unclear on exactly what Docker is doing and not doing. I will spend some time looking into that. What is it doing in particular for LedgerSMB and just for this project only, can some kind of temporary workaround be used? Can I go ahead and port all of the missing modules and pass/fail the existing tests until something can be done about the Docker problem? OpenBSD has recently done a lot of work to make porting much easier to do. I do see that a lot of projects are using Docker, so it may be worth the effort to get it working in OpenBSD. People are using it with an Alpine Linux vmm from OpenBSD, but I have no experience in that. Chris Bennett

1 0

LedgerSMB packages in Debian
by Robert J. Clay 06 Apr '19

06 Apr '19

Note that due to illness; although I updated our 'ledgersmb-1.6' pkg for v1.6.10 I haven't yet updated the 'ledgersmb' pkg for that version so what's in Debian Testing is still only v1.6.9. And since the hard freeze in preparation for the Debian release of Buster as the new stable has gone active, there is no more auto migration to Testing for updated packages in Debian unstable until after the new version has been released. Besides still waiting for the last 3 debconf translations so that the pkg can be updated with them, I've also been thinking about a major change in the package; that being changing it so that it uses the dojo distributed in the LedgerSMB archive instead of that in Debian like is already being done with our 'ledgersmb-1.6' package, on the basis that the version in Debian is not the same as that actually being used by the app itself. There's not that much of a dojo related version difference with what LedgerSMB 1.6 uses (Debian testing has v1.14.2) but that's not the case for LSMB 1.7 so it's something I need to look at in any case. A ledgersmb package with major changes could always be uploaded to Debian Experimental (& our package repos, of course), so that's what I'll be looking at doing if necessary. Related to that is still getting the autopkgtest functionality done for the package. That (which does 'as installed' testing) is useful I think in any case but in particular having to do related to the different dojo versions. But that is based on my thinking that the JS code is actually being at least somewhat exercised in the 't/' and or 'xt/' testing, which I was wondering about due to something one the other devs said/ but which I've been assured that the JS code is being exercised in the bdd tests in xt/. So I figure to work on getting the t/ tests working for the autopkgtest to start off with and continue from there to the xt/ tests. Any comments/questions/etc, please let know. -- Robert J. Clay jame(a)rocasa.us rjclay(a)gmail.com

3 3

ledgersmb is marked for autoremoval from testing
by Debian testing autoremoval watch 23 Mar '19

23 Mar '19

ledgersmb 1.6.9+ds-1 is marked for autoremoval from testing on 2019-04-13 It (build-)depends on packages with these RC bugs: 923905: libdbd-pg-perl: FTBFS (failing tests)

2 1

Release of ledgersmb-1.6 package v1.6.10-1
by Robert J. Clay 20 Jan '19

20 Jan '19

An initial version of the debian ledgersmb-1.6 package version for LedgerSMB v1.6.10 has been created and uploaded to our PPA[1], for Ubuntu 'disco' (v19.04) and 'cosmic' (v18.10) as well as for '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. (They depend on their respective web proxy applications and attempt to do at least some setup for them.) Note that I haven't created a ledgersmb-1.6 package yet at our apt package repository[2] for Debian 'Buster' (which is expected to be Debian v10) as that Debian version has not yet been released. It is, however, expected later this year so if people would like that I start making it available as well, please let me know. -- 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 [2] https://apt.ledgersmb.org/

1 0

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 31 Dec '18

31 Dec '18

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 28 Dec '18

28 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 28 Dec '18

28 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 26 Dec '18

26 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 26 Dec '18

26 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

LedgerSMB 1.6.9 released
by Erik Huelsmann 26 Dec '18

26 Dec '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. Please note that this version fixes an bug where unsuspecting users could make accounting mistakes: sales taxes not correctly included in the amount due for purchase invoices. The bug is present in all 1.5 version prior to 1.5.24 and all 1.6 releases prior to 1.6.9. Also note that AP Transactions are not affected by this bug and have been working correctly in 1.5 and 1.6 releases. This release contains the following fixes and improvements: Changelog for 1.6.9 * Fix all addresses selected on AR/AP Invoice's Ship To screen (Erik H, #3940) * Fix sales tax not included in amount due on purchase invoice (Erik H, #3941) * Fix selected sales person not showing correctly on AR Invoice (Erik H, #3949) * Fix invoice selected shipping address not showing as selected (Erik H, #3899) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.9/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.9 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.9 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.9 These are the sha256 checksums of the uploaded files: 506aa3457d8b14eb2a2f55220c87f424e8dc52647469f781cf91a26ce6f41fb2 ledgersmb-1.6.9.tar.gz 50e93233f89de59fe236790ea20e49e1612642cf737d7bb6849be1b475d50a23 ledgersmb-1.6.9.tar.gz.asc

1 0

LedgerSMB 1.5.24 released
by Erik Huelsmann 26 Dec '18

26 Dec '18

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. Please note that this version fixes an bug where unsuspecting users could make accounting mistakes: sales taxes not correctly included in the amount due for purchase invoices. The bug is present in all 1.5 version prior to 1.5.24. Also note that AP Transactions are not affected by this bug and have been working correctly in 1.5 releases. This release contains the following fixes and improvements: Changelog for 1.5.24 * Fix all addresses selected on AR/AP Invoice's Ship To screen (Erik H, #3940) * Fix sales tax not included in amount due on purchase invoice (Erik H, #3941) * Fix selected sales person not showing correctly on AR Invoice (Erik H, #3949) * Fix invoice selected shipping address not showing as selected (Erik H, #3899) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.5.24/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.5.24 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.24 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.24 These are the sha256 checksums of the uploaded files: 1c9c54a707b1404c4296eec4cf7eda364caf11928d56c96ad3f2fd6da1a67563 ledgersmb-1.5.24.tar.gz 778244fe73db36ccb8fd5b6217c29e909807544cef226c290cb2d7de9e347451 ledgersmb-1.5.24.tar.gz.asc

1 0

ledgersmb 1.6.8+ds-1 MIGRATED to testing
by Debian testing watch 21 Dec '18

21 Dec '18

FYI: The status of the ledgersmb source package in Debian's testing distribution has changed. Previous version: 1.6.6+ds-2 Current version: 1.6.8+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