Martin, thank you for the clarification!
And what about the documentation? Will you create new google docs for V3? I think so far the biggest affected part if beanquery, but I notice that also other part of the extensive documentation set is affected here and there by changes to V3 On Sunday, June 16, 2024 at 10:22:59 PM UTC+2 [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/e712158a-e1e2-4d0d-a9ae-d2a5b7e1085an%40googlegroups.com.
