Notes

Pavel Kulbakin

Pavel Kulbakin's Notes

Pavel Kulbakin

Pavel Kulbakin

December 01 2013
From now on, i will submit all commits and code improvements into my own anahita fork https://github.com/kulbakin/anahita due to the fact it's not always clear what is bug and what is improvement and to what extent. Check fork's readme for additional info. Everybody is welcome to cherrypick http://git-scm.com/docs/git-cherry-pick whatever you like.
Rastin Mehr
Rastin Mehr
December 01 2013 Permalink
Here http://www.getanahita.com/pages/128203-how-to-report-bugs If you have suggestions to improve the process, please comment on the page. Basically you pick a high priority bug from the todo list and fix it and then do a pull request.
Pavel Kulbakin
Pavel Kulbakin
December 01 2013 Permalink
@rastin everything i commit to my fork i consider beneficial to anahita, project specific features i keep in my private anahita application. I need those fixes and improvements anyway, so there is not much to discuss:) that's why i suggested you to keep an eye on changelog and import any features or fixes you find indeed required. You can always ask me about any of the commits here or better yet in issue tracker of the fork https://github.com/kulbakin/anahita/issues
Rastin Mehr
Rastin Mehr
December 01 2013 Permalink
that's one way of doing it, because we don't include all the incoming pull requests. It is good that you are maintaining your own fork as well. That's the whole idea of GitHub. I sent out a hangout call to everyone. Would love to hear your suggestions and comments as well. Thank you Pavel.
Rastin Mehr
Rastin Mehr
December 01 2013 Permalink
Also while we appreciate the improvements that you suggest if you could please select from the existing high priority bugs on the todo list and fix those, it would be great help to the Anahita project. Because that will help us get to the Birth release faster.

Powered by Anahita