- devel - lists.freelock.com

Bumping minimum required perl for master/1.7: requiring at least 5.18
by Erik Huelsmann 06 May '18

06 May '18

Hi, In the chat we just discussed that 5.18 has been released in 2014 and is long past its support timeframe. In order to prune the ever-growing number of combinations to test on, we're eliminating Perl 5.14 and 5.16 from the test framework and from the list of supported versions, making 5.18 the lowest supported Perl version for 1.7 whenever it gets released. (Note: we can always decide to choose a higher minimum number, if it takes too long to finish 1.7.) Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

1.6.0-beta1 uploaded for general testing
by Erik Huelsmann 06 May '18

06 May '18

Hi, This is to let you know that I've just finished uploading LedgerSMB 1.6.0beta1 (taken from our repository at commit hash 9956baac) for early-bird testing and evaluation purposes to https://download.ledgersmb.org/f/Beta%20Releases/1.6.0-beta1/ . Note that the difference between the uploaded tar and the git commit is that the tar contains our minified Dojo Toolkit dependency. Among other things, we'll be using this upload to develop our Docker images before the final 1.6.0 release. You're encouraged to do the same with any dependencies and/or packaging procedures you may have and report your problems either to devel(a)lists.ledgersmb.org or in the GitHub issue tracker. Before filing a ticket, please check if a similar issue has already been filed. The changelog for the 1.6 release series can be found here: https://github.com/ledgersmb/LedgerSMB/blob/1.6/Changelog#L2-L59 -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

[ANNOUNCE] 1.6 ready for translation
by Erik Huelsmann 05 May '18

05 May '18

Hi, This is an announcement for translators: on Friday we branched 1.6 and prepared it for translation. We expect to release 1.6.0 late this quarter or early next quarter. Although translations can be done any time, releasing 1.6.0 with complete translations makes for a much better impression on new users of course. To those who aren't translators yet: this is an opportunity to contribute to the project! It's easy to become a LedgerSMB translator by navigating to https://www.transifex.com/ledgersmb/ledgersmb/dashboard/ , click on the "Help translate LedgerSMB" button and follow the sign-up steps. If you have any questions regarding translation, please post to devel(a)lists.ledgersmb.org. Regards, Erik

1 0

Proposal to branch 1.6
by Erik Huelsmann 04 May '18

04 May '18

Hi, Over at the LedgerSMB chat channel, we've been considering branching 1.6 to start its stabilization period. With the merge of the most blocking prerequisites this weekend (infrastructure to develop pre-upgrade tests which run before schema&version upgrades) and with the impressive Changelog as listed below "now" feels like a natural branchpoint. We've taken a look at the issues which are marked to block 1.6 ( https://github.com/ledgersmb/LedgerSMB/issues?q=is%3Aopen+is%3Aissue+label%…) Of the three issues listed there, one (#2432) can easily be backported to the release branch as it simply inverts the meaning of a checkbox. The same applies to #3363, which is a development-half-finished on my part; it can probably be closed pretty quickly as all that needs to be done is add an extra field on all INSERTs into the GL table. The last issue (#1077) looks like it's pretty large and won't be able to make it into 1.6, unless there's someone to step up and invest a significant amount of time in it in the coming weeks. Here, we think delaying to the next release (and working on a representative test-set to show the problem) is likely the only option we have as a project. All-in-all, we seem to be at a natural point for branching 1.6. Comments? Remarks? Changelog for 1.6 Series Forthcoming User Interface * Reports and search results exportable to XLS(X) (Yves L) * Left menu replaced by a (faster) Dojo-based version (Yves L/Erik H) Installation & Administration * Added 'System Information' page to setup.pl for problem diagnosis (Erik H) * Numerous improvements for the migrations and infrastructure (Yves L/Erik H) * Better detection of incorrect @INC paths (David G) * Automatic date format selection using browser locale (Yves L/Erik H) * No more warnings from database creation and upgrade (Erik H) * Improved logging: various logs correlated using unique request IDs (Erik H) * Functions 'warn()' and 'die()' logged to debug logs (Erik H) * Removed need for 'tempdir' and associated configuration option (Nick P) * Removed numerous unused configuration options (Nick P) * Specific output formats can be disabled in configuration (Yves L) * Respect smtpuser and smtppass configuration options (Nick P) * Add smtpport configuration option (Nick P) Performance * PSGI responses no longer written to file but kept in memory (Erik H/Yves L) Rewritten inventory tracking and adjustments * Removed the need for the ill-understood 'Inventory Entity' (Erik H) * Inventory adjustments GL transactions instead of dummy invoices (Erik H) * SQL & in-browser(BDD) tests (Erik H) Code cleanup * Removed code duplication in - Template handling framework (Yves L) * Remove unused variables and unreachable code (Nick P) * Remove fragments of REST framework never fully implemented (Erik H) * Authentication handling centralized in request dispatch code (Erik H) * Cleaned up handling of uploaded files in request handling (Erik H) * Moved to Plack::Request (from CGI::Simple & LedgerSMB) (Erik H) * Template format plugin cleanup and refactoring (Erik H/Nick P) * Template handling code cleanup (Erik H/Nick P) * Unreferenced UI templates deleted (Erik H) * Centralized and more robust entry point for code in old/ (Erik H) * Merge of SQL-Ledger 2.8 and 3.0 migration code; improved consistency (Yves L) * Improved cleanup of temp files and dirs after use (Erik H) * Improved HTML structure (balanced closing/opening tags, etc) (Yves L) * Factored HTTP response responsibility out of LedgerSMB::Template (Erik H) * Moved request pre- and post-processing into custom Plack Middlewares (Erik H) Quality assurance * Port testing of database routines to pgTAP (and Perl's 'prove') (Yves L) * Enforce numerous Perl::Critic policies with code cleanup (Nick P/Rob R) * Add tests for all template output formats (Nick P) Erik H is Erik Huelsmann Yves L is Yves Lavoie Nick P is Nick Prater Rob R is Rob Ransbottom David G is David Godfrey -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

Which corrective action for "invoice COGS schema check"?
by Erik Huelsmann 30 Apr '18

30 Apr '18

Hi, After having merged the infrastructure to check data validity in an existing database before applying an upgrade script, I'm reviewing existing scripts to see if they may qualify to be enhanced with a check and user intervention. One script which qualifies is 1.5/invoice-tbl-cogs-constraint.sql which adds a constraint verifying that the COGS routines post data which makes sense. Existing data does not necessarily comply with the new constraint. I wonder though what corrective action to offer a user who is the proud owner of non-compliant data. I see a number of options: 1. Tell the user to contact the mailing list (and block his migration in the mean time) 2. Modify the data to be within the bounds to be enforced (and thereby loose the COGS audit trail? 3. Allow constraint creation to fail by modifying Loadorder and create a new script which creates a "not valid" constraint (which allows the existing data to remain in place, but verifies new data) 4. Create a check script which creates the "not valid" constraint and fakes script application by modifying dbchanges tables 5. Adjust the data back into bounds, allocating the overage to more recent invoices and creating a COGS adjustment journal which the admin must post Which should we go with? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 2

Release of ledgersmb-1.5 v1.5.20-1
by Robert J. Clay 14 Apr '18

14 Apr '18

An initial version of the debian package ledgersmb-1.5 for version 1.5.20-1 has been released and uploaded to our apt repository for 'main' in stretch[1]. It has also been uploaded to our PPA[2], for 'artful' (v17.10) as well as 'xenial (v16.04) and 'bionic (which will be v18.04). (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. -- 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 1.5.20 released
by Erik Huelsmann 14 Apr '18

14 Apr '18

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.20 * Fix inability to save custom sequences (System > Sequence) (Erik H, #3511) * Fix error when downloading balance sheet as PDF (Erik H, #3515) * Fix empty backup file due to PGObject::Util::DBAdmin 0.120 (Erik H, #3531) * Norwegian (nb) translation update (Havard S) Erik H is Erik Huelsmann Havard S is Havard Sorli For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.5.20/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.5.20 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.20 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.20 These are the sha256 checksums of the uploaded files: bb815d97b23707c6f70b1a5cac56adb86fd0c841a5c4b403770760fee1a8392c ledgersmb-1.5.20.tar.gz 8931bac54f7b877486629fdf296968ad1b93bed11067116db8cbe531cecc4625 ledgersmb-1.5.20.tar.gz.asc

1 0

Refined label definitions
by Erik Huelsmann 14 Apr '18

14 Apr '18

Hi, After review of our issue labels and their use, I've changed the wording ( https://github.com/ledgersmb/LedgerSMB/wiki/Issue-labels) of the for the labels "blocking" and "started". Blocking now reads: Deemed "needs to be fixed before the assigned release"; issues in this category apply to unacceptable regressions or critical (non-accounting) bugs -- in general, issues preventing work from getting done The change here is the last sentence having been added "in general, issues preventing work from getting done" Started now reads: Work on this issue has started and the issue is actively being worked on The change here is the "and" clause having been added: "and the issue is actively being worked on". -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

HEADS UP: New development container due to changed dependencies for master
by Erik Huelsmann 13 Apr '18

13 Apr '18

Hi, Earlier today, I've changed tthe dependency on File::MimeInfo to MIME::Types due to the fact that the former depends on freedesktop.org while the latter has its own MIME database built in, thus reducing the number of external dependencies. To accomodate this changed dependency, I've triggered a build for the DEV-container, which should finish in ~30 minutes from now. Please update your development environments. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.5.19 released
by Erik Huelsmann 02 Apr '18

02 Apr '18

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.19 * Fix payment screen localized amount formatting problem (Erik H, #3283) * Separate error and output 'psql' logs during database upgrade (Nick P) * Fix random order of PNL and B/S reports columns (Erik H, #2244) * Various fixes to setup.pl regarding backup file generation (Nick P) * Use File::Path to create directory instead of through shell call-out (Nick P) * On TAB-exit of accounts/parts selector, select first item (Erik H) * Estonian translation update (Margus L) * German translation update (Mikael A) * Hungarian translation update (Istvan P) Erik H is Erik Huelsmann Nick P is Nick Prater Istvan P is is Istvan Pongracz Margus L is Margus Lepmets Mikael A is Mikael Arhelger For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.5.19/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.5.19 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.19 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.5.19 These are the sha256 checksums of the uploaded files: 7dba20470984328924ba3ef3dd3d92b60f41b6023ccbe72d107968da0cb1c677 ledgersmb-1.5.19.tar.gz 40f2f458a6605f05ee1eb238f0c084c481cd26273287568f35b927b75813665c ledgersmb-1.5.19.tar.gz.asc

1 0