release stores all payments as separate data items specifically, considerably changing reconciliation experience. 1.7.0 (End of Life) was released on 2019-10-04 with improved support for transactions in foreign currencies, much code cleanup and yet more tests again. With the 1.7.0 release, the project continues the trend to shorten the cycle between minor (.0) releases. 1.6.0 (End of Life) was released on 2018-06-10 with a change log focused on stability and a code base to build a future on. 1.5.0 (End of Life) was released on 2016-12-24 with a change log focused on stability and user experience. 1.4.0 (End of Life) was released on 2014-09-15 with another sizeable change log. The 1.3.0 (End of Life) release came out on 2011-10-11, with a sizeable change log, generally focusing on performance, separation of duties and fixing the (design) issues in 1.2. The 1.2.0 (End of Life) release (announced on 2007-04-06) included a number of very deep security fixes and the beginnings of the refactoring process. The tax and price matrix code was centralized. This release was quite problematic and the core team ended up pulling 1.2.0 and 1.2.1 from public distribution due to a number of issues in integrating old and new code. Many members of the core team have expressed frustration at the level of problems, but Chris Travers has generally compared the problems to those of Apache 2.0, where changes in architecture have caused problematic releases. The general hope is that 1.2.x will be the most difficult and problematic release, perhaps of all time. At the same time, it cannot be denied that a number of the problems in 1.2.0 were the result of trying to do too much too quickly without adequate review. The 1.1.0 release merged in many patches that had been done for other customers but did not change the structure of the code in any significant way. By this time, however, most of the core members were unhappy with the current architecture and had decided to work on refactoring the code. The initial release (1.0.0 on 2006-09-06) and the events leading up to it, are described in the History section. 1.5+ Developments As of 1.5, development has taken a direction to move to a heavier (in-browser) client with access to web services in the backend. To that extent, the 1.5 UI has been realiZed as a single-page web application. The result is a (much) more responsive experience