I'd forgotten the tag. There's one now. On Mon, Jun 17, 2024 at 7:33 AM Martin Blais <bl...@furius.ca> wrote:
> On Mon, Jun 17, 2024 at 6:00 AM Brian Lalor <bjl_...@bravo5.org> wrote: > >> This is great! Thank you! Is there a summary of what’s new/different in >> 3.0.0 from 2.3.6? (Also I don’t see a 3.0.0 tag in GitHub; was that an >> oversight?) >> > > v3 > - removes beanquery, beanprice, beanweb and more, is pretty stripped down. > Use the subprojects instead. > - has a number of really minor fixes added over time but no major new > features > If you were using the 'master' branch there's no change. > > You should not use v2 anymore. > > > > >> -- >> Brian Lalor (he/him) >> bla...@bravo5.org >> >> On Jun 16, 2024, at 4:23 PM, Martin Blais <bl...@furius.ca> wrote: >> >> >> Based on our recent discussion around Beancount branches being confusing, >> I did the following to branches: >> >> - v2: remains the same (no change); but v2 is now even less subject to >> freeze exceptions than before, because v3 is now officially born and PyPI >> releases will be made for it. The default reply to patches to v2 will be >> "move that to v3." >> >> - cpp: I turned the previous master branch's state with all C++ and Bazel >> build into a new 'cpp' branch. >> All work on the C++ rewrite -- if it is to continue -- will live on >> that branch. >> If things do move to Rust, I will probably salvage bits and pieces of >> that manually into a 'rust' branch. >> In particular, the schema defined in the proto files is something I'd >> like to carry forward (nicely >> documented and distinguishes between the pre and post interpolation >> data structures explicitly), >> and perhaps the new reFlex parser will be useful at some point. >> >> - v3: a new branch, to contain the state of the master branch MINUS the >> C++ bits. >> As stated above, the C++ code remains only on branch 'cpp'. >> This is now the official release branch and PyPI releases will be made >> of it. >> >> - master: this branch is now where new work on v3 might live. >> I'm not sure we really need it or what it should mean, but it should >> track v3 for now. >> >> I've reviewed missing PyPI releases and made sure we have these: >> >> https://pypi.org/project/beancount/ >> https://pypi.org/project/beangulp/ >> https://pypi.org/project/beanquery/ >> https://pypi.org/project/beanprice/ >> https://pypi.org/project/beangrow/ >> https://pypi.org/project/beancount2ledger/ >> >> The inclusion of v3 releases for PyPI and new PyPI releases for >> subprojects should normalize the versioning situation in Beancount. Note >> that packaging and following other people's conventions are not my forte >> (and I don't use PyPI for my own projects I just use source), if you have >> any suggestions or something's missing please reply to this thread. >> >> Thanks for your patience, >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/CAK21%2BhNfFy-Y%3DiOgnNLFf04c42b4hBiqgfcjGCx-re2H02y_ww%40mail.gmail.com >> <https://groups.google.com/d/msgid/beancount/CAK21%2BhNfFy-Y%3DiOgnNLFf04c42b4hBiqgfcjGCx-re2H02y_ww%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/5246A8C0-336D-4B5C-8FE8-D95BF7E23C7C%40bravo5.org >> <https://groups.google.com/d/msgid/beancount/5246A8C0-336D-4B5C-8FE8-D95BF7E23C7C%40bravo5.org?utm_medium=email&utm_source=footer> >> . >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhO3KqQ9qq4tk4o1qYqugbDNWE8zHnpMCqaXi6O7oKPpTQ%40mail.gmail.com.
