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 feedback, insightful conversations, > and allow me access to the official Ledger repository. Thanks John! > > I am committed to do what I can to move Ledger forward, my main focus > is getting rid of the segmentation faults, adding more tests, improving > the documentation by covering all available options, and expanding the > Python module. > > John and I have been talking about various aspects and which need > more work and I am currently planning what issues should be addressed > for the next release (3.1.1). > I am uncertain who has a say (apart from John ;) in deciding what bugs > should be fixed and which features implemented, so make yourself > heard and let's talk about important issues to plan a roadmap. > > John and I agreed to keep all P1 bugs (8 in total) and moved all P2 bugs > to P3, so I can move bugs I feel should be addressed for Ledger 3.1.1 > back to P2 and start working on it. > Since I'm not yet too familiar with all aspects of Ledger I will > also address minor bugs that I think will help me in digging deeper > into Ledger's code. > > I found 23 segmentation fault related bugs in Bugzilla and I would like > to set their Status to UNCONFIRMED, then go through them one by one > and schedule the ones that can be reproduced with a master build for > 3.1.1 and set their Status to CONFIRMED. > > 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 on. > > You're more than welcome to help out if you can by contributing patches, > going through Bugzilla verifying that bugs are still reproducible, > sharing your knowledge so you or someone else can document it, add > tests, tell your story with Ledger, share ideas or cool things you've > done with Ledger, the community and Ledger will benefit from you > contribution. > > It would be great if we can coordinate our work to gain the most from > our joint effort and I invite you to talk to me; I'm afh in #ledger. > > > Thanks, > Alexis > > > น http://nvie.com/posts/a-successful-git-branching-model/ > https://github.com/nvie/gitflow > > -- > > --- > 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 https://groups.google.com/d/optout. > -- Craig, Corona De Tucson, AZ enderw88.wordpress.com -- --- 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 https://groups.google.com/d/optout.
