Re: Further Ledger Development

2015-01-07 Thread Alexis
Hi John, the way I understand git-flow is that for frequent pre-releases the release branches are used, so master always points to the last stable release, currently this would be release/3.1.0 (created from the v3.1 tag). As development on 3.1.1 begins a branch named release/3.1.1 is created

Re: Further Ledger Development

2015-01-07 Thread Martin Blais
Actually, the command-line accounting cookbook uses Beancount for its example syntax but applies to Ledger just as well (which is why I called it the command-line accounting cookbook and not the Beancount cookbook'): http://furius.ca/beancount/doc/cookbook http://furius.ca/beancount/doc/trading

Re: Further Ledger Development

2015-01-07 Thread Alexis
Hi Martin, oh wow, can't wait to read through those and try them! Maybe it's a good idea add the links to the ledger-cli.org/docs.html, what do you think? John, Simon? Cheers, Alexis -- --- You received this message because you are subscribed to the Google Groups Ledger group. To

Re: Further Ledger Development

2015-01-07 Thread John Wiegley
Alexis surryh...@gmail.com writes: Maybe it's a good idea add the links to the ledger-cli.org/docs.html, what do you think? John, Simon? Sounds good! John -- --- You received this message because you are subscribed to the Google Groups Ledger group. To unsubscribe from this group and

Re: Further Ledger Development

2015-01-07 Thread John Wiegley
Alexis surryh...@gmail.com writes: the way I understand git-flow is that for frequent pre-releases the release branches are used, so master always points to the last stable release, currently this would be release/3.1.0 (created from the v3.1 tag). As development on 3.1.1 begins a branch

Re: Further Ledger Development

2015-01-07 Thread Alexis
Thanks all for the warm welcome =) Eric, I agree Ledger can you more documentation, I think the Ledger Cookbookš could use many more examples. If you have any gems you'd like to share please do so and if you know of any conversations on the list please share a link so we can include that

Re: Further Ledger Development

2015-01-06 Thread Craig Earls
Nice to have you aboard Alexis! I have no suggestions on bug fixes as my workflow doesn't expose any. On Tue, Jan 6, 2015 at 5:15 AM, Alexis surryh...@gmail.com wrote: Hello everyone, lately I have been providing some patches to Ledger and John was kind enough to help out with valuable

Re: Further Ledger Development

2015-01-06 Thread John Wiegley
Alexis surryh...@gmail.com writes: John and I agreed to follow the git-flowน model for development, which means the master branch will only see updates when a new version is released as of now and development will happen on the next branch, so please make pull request against next from now

Re: Further Ledger Development

2015-01-06 Thread Eric Abrahamsen
Alexis surryh...@gmail.com writes: Hello everyone, lately I have been providing some patches to Ledger and John was kind enough to help out with valuable feedback, insightful conversations, and allow me access to the official Ledger repository. Thanks John! I am committed to do what I can

Re: Further Ledger Development

2015-01-06 Thread Simon Michael
That's exciting news, great work Alexis. -- --- You received this message because you are subscribed to the Google Groups Ledger group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. For more options, visit