Hi, Martin.

I totally get the "undisturbed time". Have a toddler of my own and that put 
pretty much all of my side projects to a halt. Please take your time. We 
all appreciate all the effort and hours you and other put into this.

That being said, I think it would really help us all (the community and 
yourself) if you (or some contributor closer to the development) could 
write down some of those milestones you have in mind, perhaps using 
GitHub's own project feature [1]. If nothing else, that would help avoid 
questions such as mine. Just to be clear, I'm not asking for any dates or 
anything, just for (some) visibility, to get a sense of the progress of the 
rewrite. Finally, please let us all know once some of those milestones have 
properly defined scopes and boundaries, so others can jump in to help in a 
more structured/productive way.

Thanks!

@Dan, I'm talking about the section entitled "Input Split Transactions" in 
the "Beancount - V3: Goals & Design" document [2].

[1] 
https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects
[2] 
https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit#

On Wednesday, September 7, 2022 at 7:43:26 PM UTC-3 [email protected] wrote:

> On 06/09/2022 03:30, Thiago Lima wrote:
> > I'm new to Beancount and PTA in general and tried v2, but would really 
> > like to leverage some of the v3 proposed features, especially the input 
> > split support.
>
> What do you mean with "input split support"? Beancount v2 has an include 
> directive (although one with a bit of a surprising semantic).
>
> Which other features of Beancount v3 would you like to use?
>
> Cheers,
> Dan
>
>

-- 
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/8b96d187-0c1d-4a59-bb54-cfa2658bc64fn%40googlegroups.com.

Reply via email to