How would you feel about me baking an official 2.0 stamp on the current tip? I was waiting to finish the doc integration to do this and adopt semantic versioning.
I don't think I will wait to close all the tickets before I make numbered releases. It's been pretty stable and I don't have enough bandwidth these days. Here's what I see is next in terms of "small stuff" that would be part of near upcoming 2.x releases: - Integrate Dominik's docs as a static copy. - Adding coherent cmdline options to disable the caches (pickle cache, price source cache, implement import cache for costly conversions). - Remove the Holding class (less code); replace all its functionality by aggregation of positions. Rewrite all the reports with SQL queries only. - Promote list_holdings.py (the script I use myself) to the main codebase and share an example Google Sheets doc to track assets (that's what I've been doing for years, works great). - Figure out what to do about speed (we need something like a 3x speedup IMO). - Do something about price sources now that G and Y finance are gone (perhaps just provide a helpers library instead of a tool, not sure) This is small-ish stuff that gets on my own nerves regularly. Here's some stuff that's being requested regularly by others that I also would like to work on: - Adding options to override / take priority over inference for precision and allow you to set the num digits to render directly. - Take a solid look at the CSV importer contributions waiting in PRs. - Implement AVERAGE booking. - Implement query assertions to have a good budget story / take time to check out Fava's custom directive for that, maybe integrate. - Supporting UTF8 and of course, slowly work my way through all those tickets and pending PRs. There's work for three dozen lifetimes (I don't suggest wading through the TODO file, you'll need courage and it's organized like a 14 year old's bedroom). Overall I'd like to reduce the amount of code (deprecate Holdings, perhaps delete bean-web (because Fava, if it can be baked), factor out SQL query client to a configurable row-based query tool that works on any data source) and focus on doing more with a smaller body of code (e.g. compute returns, support complex risk calculations (I hold options), implement pivot table in SQL for e.g. monthly reports, make the shell so powerful it's the only way to generate reports, simplify the tags/links schema, etc.). On Fri, Mar 23, 2018 at 10:00 AM, Martin Michlmayr <t...@cyrius.com> wrote: > 2.0rc1 is almost a year old. Would it be possible to cut an rc2 since > there have been a lot of changes in the meantime? > > This would help those not installing from mercurial directly. > > Thanks, > > Reference: > https://pypi.org/project/beancount/#history > -- > Martin Michlmayr > http://www.cyrius.com/ > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beancount+unsubscr...@googlegroups.com. > To post to this group, send email to beancount@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beancount/20180323140005.4y4rquuqigi7mgts%40jirafa.cyrius.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhM_sHSBRpGVhi-GTeYd-yCKwdjePpigCsSdXRDQK3afiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
